Devices, Methods, and Graphical User Interfaces for Adjusting User Interface Objects

ABSTRACT

An electronic device displays a user interface that includes one or more user interface elements. The device detects a contact on a touch-sensitive surface. The device detects a first increase in a characteristic intensity of the contact. In response to detecting the first increase, the device adjusts a property of a first user interface element from a first value to a second value. After adjusting the property, the device detects a decrease in the characteristic intensity of the contact. In response to detecting the decrease, in accordance with a determination that the first increase met intensity criteria, the device maintains the property above the first value. After detecting the decrease, the device detects a second increase in the characteristic intensity of the contact. In response to detecting the second increase, the device adjusts the property to a third value that is greater than the second value.

RELATED APPLICATIONS

This application claims priority to: (1) U.S. Provisional ApplicationSer. No. 62/235,339, filed Sep. 30, 2015, entitled “Devices, Methods,and Graphical User Interfaces for Adjusting User Interface Objects”; and(2) U.S. Provisional Application Ser. No. 62/203,387, filed Aug. 10,2015, entitled “Devices, Methods, and Graphical User Interfaces forManipulating User Interface Objects with Visual and/or Haptic Feedback,”both of which are incorporated by reference herein in their entireties.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that detect inputs for adjusting user interfaceobjects.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Exemplary touch-sensitive surfaces include touchpads andtouch-screen displays. Such surfaces are widely used to manipulate userinterface objects on a display.

Exemplary manipulations include adjusting the position and/or size ofone or more user interface objects. Exemplary user interface objectsinclude control elements such as buttons, sliders, and other graphics;digital images; video; text; and icons. A user will, in somecircumstances, need to perform such manipulations on user interfaceobjects in a digital content (e.g., videos and music) managementapplication (e.g., iTunes from Apple Inc. of Cupertino, Calif.), animage management application (e.g., Aperture, iPhoto, Photos from AppleInc. of Cupertino, Calif.), a document reader application (e.g., iBooksfrom Apple Inc. of Cupertino, Calif.), or a communications managementapplication (e.g., a messaging, e-mail, or telephone application).

But existing methods for performing these manipulations are cumbersomeand inefficient. For example, using a sequence of mouse based inputs toselect one or more user interface objects and perform one or moreactions on the selected user interface objects is tedious and creates asignificant cognitive burden on a user. In addition, these methods takelonger than necessary, thereby wasting energy. This latter considerationis particularly important in battery-operated devices.

SUMMARY

Accordingly, there is a need for electronic devices with faster, moreefficient methods and interfaces for adjusting properties of displayeduser interface elements. Such methods and interfaces optionallycomplement or replace conventional methods for adjusting properties ofdisplayed user interface elements. Such methods and interfaces reducethe number, extent, and/or nature of the inputs from a user and producea more efficient human-machine interface. For battery-operated devices,such methods and interfaces conserve power and increase the time betweenbattery charges.

Additionally, there is a need for electronic devices with faster, moreefficient methods and interfaces for adjusting a property of a userinterface object.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device is a personal electronic device(e.g., a wearable electronic device, such as a watch). In someembodiments, the device has a touchpad. In some embodiments, the devicehas a touch-sensitive display (also known as a “touch screen” or“touch-screen display”). In some embodiments, the device has a graphicaluser interface (GUI), one or more processors, memory and one or moremodules, programs or sets of instructions stored in the memory forperforming multiple functions. In some embodiments, the user interactswith the GUI primarily through stylus and/or finger contacts andgestures on the touch-sensitive surface. In some embodiments, thefunctions optionally include image editing, drawing, presenting, wordprocessing, spreadsheet making, game playing, telephoning, videoconferencing, e-mailing, instant messaging, workout support, digitalphotographing, digital videoing, web browsing, digital music playing,note taking, and/or digital video playing. Executable instructions forperforming these functions are, optionally, included in a non-transitorycomputer readable storage medium or other computer program productconfigured for execution by one or more processors.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface, and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface. The method includes: displaying, on the display, a userinterface that includes: a slider that corresponds to a first range ofvalues, and one or more other user interface objects; detecting acontact on the touch-sensitive surface while a focus selector is at theslider; detecting a first increase in a characteristic intensity of thecontact on the touch-sensitive surface while the focus selector is atthe slider; and, in response to detecting the first increase in thecharacteristic intensity of the contact on the touch-sensitive surfaceand in accordance with a determination that the characteristic intensityof the contact meets intensity criteria: displaying an expanded portion,less than all, of the slider while maintaining an appearance of the oneor more other user interface objects.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface, and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface. The method includes: displaying, on the display, a userinterface that includes one or more user interface elements; detecting acontact on the touch-sensitive surface; and, while detecting the contacton the touch-sensitive surface: detecting a first increase in acharacteristic intensity of the contact on the touch-sensitive surface;in response to detecting the first increase in the characteristicintensity of the contact, adjusting a property of a first user interfaceelement of the one or more user interface elements in the user interfacefrom a first value to a second value; after adjusting the property ofthe first user interface element, detecting a first decrease in thecharacteristic intensity of the contact; in response to detecting thefirst decrease in the characteristic intensity of the contact, inaccordance with a determination that the first increase in thecharacteristic intensity of the contact met intensity criteria,maintaining the property of the first user interface element above thefirst value; after detecting the decrease in the characteristicintensity of the contact and while the property of the first userinterface element is above the first value, detecting a second increasein the characteristic intensity of the contact; and, in response todetecting the second increase in the characteristic intensity of thecontact, adjusting the property of the first user interface element to athird value that is greater than the second value.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a user interface, a touch-sensitivesurface unit to receive contacts, one or more sensor units to detectintensity of contacts with the touch-sensitive surface unit; and aprocessing unit coupled with the display unit, the touch-sensitivesurface unit, and the one or more sensor units. The processing unit isconfigured to: enable display, on the display unit, of a user interfacethat includes: a slider that corresponds to a first range of values, andone or more other user interface objects; detect a contact on thetouch-sensitive surface unit while a focus selector is at the slider;detect a first increase in a characteristic intensity of the contact onthe touch-sensitive surface unit while the focus selector is at theslider; and, in response to detecting the first increase in thecharacteristic intensity of the contact on the touch-sensitive surfaceunit and in accordance with a determination that the characteristicintensity of the contact meets intensity criteria: enable display of anexpanded portion, less than all, of the slider while maintaining anappearance of the one or more other user interface objects.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a user interface, a touch-sensitivesurface unit to receive contacts, one or more sensor units to detectintensity of contacts with the touch-sensitive surface unit; and aprocessing unit coupled with the display unit, the touch-sensitivesurface unit, and the one or more sensor units. The processing unit isconfigured to: enable display, on the display unit, of a user interfacethat includes one or more user interface elements; detect a contact onthe touch-sensitive surface unit; and, while detecting the contact onthe touch-sensitive surface unit: detect a first increase in acharacteristic intensity of the contact on the touch-sensitive surfaceunit; in response to detecting the first increase in the characteristicintensity of the contact, adjust a property of a first user interfaceelement of the one or more user interface elements in the user interfacefrom a first value to a second value; after adjusting the property ofthe first user interface element, detect a first decrease in thecharacteristic intensity of the contact; in response to detecting thefirst decrease in the characteristic intensity of the contact, inaccordance with a determination that the first increase in thecharacteristic intensity of the contact met intensity criteria, maintainthe property of the first user interface element above the first value;after detecting the decrease in the characteristic intensity of thecontact and while the property of the first user interface element isabove the first value, detect a second increase in the characteristicintensity of the contact; and, in response to detecting the secondincrease in the characteristic intensity of the contact, adjust theproperty of the first user interface element to a third value that isgreater than the second value.

In accordance with some embodiments, an electronic device includes adisplay, a touch-sensitive surface, optionally one or more sensors todetect intensity of contacts with the touch-sensitive surface, one ormore processors, memory, and one or more programs; the one or moreprograms are stored in the memory and configured to be executed by theone or more processors and the one or more programs include instructionsfor performing or causing performance of the operations of any of themethods described herein. In accordance with some embodiments, acomputer readable storage medium (e.g., a non-transitory computerreadable storage medium, or alternatively, a transitory computerreadable storage medium) has stored therein instructions which whenexecuted by an electronic device with a display, a touch-sensitivesurface, and optionally one or more sensors to detect intensity ofcontacts with the touch-sensitive surface, cause the device to performor cause performance of the operations of any of the methods describedherein. In accordance with some embodiments, a graphical user interfaceon an electronic device with a display, a touch-sensitive surface,optionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface, a memory, and one or more processors to executeone or more programs stored in the memory includes one or more of theelements displayed in any of the methods described herein, which areupdated in response to inputs, as described in any of the methodsdescribed herein. In accordance with some embodiments, an electronicdevice includes: a display, a touch-sensitive surface, and optionallyone or more sensors to detect intensity of contacts with thetouch-sensitive surface; and means for performing or causing performanceof the operations of any of the methods described herein. In accordancewith some embodiments, an information processing apparatus, for use inan electronic device with a display and a touch-sensitive surface, andoptionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface, includes means for performing or causingperformance of the operations of any of the methods described herein.

Thus, electronic devices with displays, touch-sensitive surfaces andoptionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface are provided with faster, more efficient methodsand interfaces for adjusting properties of displayed user interfaceelements, thereby increasing the effectiveness, efficiency, and usersatisfaction with such devices. Such methods and interfaces maycomplement or replace conventional methods for adjusting properties ofdisplayed user interface elements.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIGS. 4C-4E illustrate exemplary dynamic intensity thresholds inaccordance with some embodiments.

FIGS. 5A-5I illustrate exemplary user interfaces for displaying anexpanded portion of a slider in accordance with some embodiments.

FIGS. 6A-6S illustrate exemplary user interfaces for adjusting aproperty of a user interface element in accordance with someembodiments.

FIGS. 7A-7D are flow diagrams illustrating a method of displaying anexpanded portion of a slider in accordance with some embodiments.

FIGS. 8A-8D are flow diagrams illustrating a method of adjusting aproperty of a user interface element in accordance with someembodiments.

FIGS. 9-10 are functional block diagrams of an electronic device inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

Users frequently seek to adjust properties of user interface elementssuch as images, control elements (such as buttons, sliders, and othergraphics), video, text, and icons. Some conventional methods foradjusting properties such as height, width, area, and time intervalrequire a user to provide input with multiple sequential or simultaneouscomponents. For example, to enlarge an image, a user selects an edge ofan image and drags the edge in a desired direction, or a user provides agesture input using multiple points of contact. Many user interfaceelements are not individually adjustable.

Here, new methods are disclosed that streamline processes for adjustingproperties of user interface elements by responding to changes in acharacteristic intensity of a contact. The methods, devices and GUIsdescribed herein provide visual and/or haptic feedback that makesmanipulation of user interface objects more efficient and intuitive fora user.

Below, FIGS. 1A-1B, 2, and 3 provide a description of exemplary devices.FIGS. 4A-4B, 5A-5I, and 6A-6S illustrate exemplary user interfaces.FIGS. 5A-5I illustrate exemplary user interfaces for displaying anexpanded portion of a slider. FIG. 6A-6S illustrate exemplary userinterfaces for adjusting a property of a user interface element. FIGS.7A-7D illustrate a flow diagram of a method of displaying an expandedportion of a slider. FIGS. 8A-8D illustrate a flow diagram of a methodof adjusting a property of a user interface element. The user interfacesin FIGS. 5A-5I and 6A-6S are used to illustrate the processes in FIGS.7A-7D and 8A-8D.

EXEMPLARY DEVICES

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact, unless the contextclearly indicates otherwise.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch-screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch-screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a note taking application, a drawing application,a presentation application, a word processing application, a websitecreation application, a disk authoring application, a spreadsheetapplication, a gaming application, a telephone application, a videoconferencing application, an e-mail application, an instant messagingapplication, a workout support application, a photo managementapplication, a digital camera application, a digital video cameraapplication, a web browsing application, a digital music playerapplication, a document reader application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display system112 is sometimes called a “touch screen” for convenience, and issometimes simply called a touch-sensitive display. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input or control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensity of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 167 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, firmware, or a combination thereof,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU(s) 120 and the peripheralsinterface 118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU(s) 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU(s) 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch-sensitive display system 112 and other input or control devices116, with peripherals interface 118. I/O subsystem 106 optionallyincludes display controller 156, optical sensor controller 158,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input or controldevices 116 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, joysticks, click wheels,and so forth. In some alternate embodiments, input controller(s) 160are, optionally, coupled with any (or none) of the following: akeyboard, infrared port, USB port, stylus, and/or a pointer device suchas a mouse. The one or more buttons (e.g., 208, FIG. 2) optionallyinclude an up/down button for volume control of speaker 111 and/ormicrophone 113. The one or more buttons optionally include a push button(e.g., 206, FIG. 2).

Touch-sensitive display system 112 provides an input interface and anoutput interface between the device and a user. Display controller 156receives and/or sends electrical signals from/to touch-sensitive displaysystem 112. Touch-sensitive display system 112 displays visual output tothe user. The visual output optionally includes graphics, text, icons,video, and any combination thereof (collectively termed “graphics”). Insome embodiments, some or all of the visual output corresponds to userinterface objects. As used herein, the term “affordance” refers to auser-interactive graphical user interface object (e.g., graphical userinterface object that is configured to respond to inputs directed towardthe graphical user interface object). Examples of user-interactivegraphical user interface objects include, without limitation, a button,slider, icon, selectable menu item, switch, or other user interfacecontrol.

Touch-sensitive display system 112 has a touch-sensitive surface,sensor, or set of sensors that accepts input from the user based onhaptic and/or tactile contact. Touch-sensitive display system 112 anddisplay controller 156 (along with any associated modules and/or sets ofinstructions in memory 102) detect contact (and any movement or breakingof the contact) on touch-sensitive display system 112 and converts thedetected contact into interaction with user-interface objects (e.g., oneor more soft keys, icons, web pages or images) that are displayed ontouch-sensitive display system 112. In an exemplary embodiment, a pointof contact between touch-sensitive display system 112 and the usercorresponds to a finger of the user or a stylus.

Touch-sensitive display system 112 optionally uses LCD (liquid crystaldisplay) technology, LPD (light emitting polymer display) technology, orLED (light emitting diode) technology, although other displaytechnologies are used in other embodiments. Touch-sensitive displaysystem 112 and display controller 156 optionally detect contact and anymovement or breaking thereof using any of a plurality of touch sensingtechnologies now known or later developed, including but not limited tocapacitive, resistive, infrared, and surface acoustic wave technologies,as well as other proximity sensor arrays or other elements fordetermining one or more points of contact with touch-sensitive displaysystem 112. In an exemplary embodiment, projected mutual capacitancesensing technology is used, such as that found in the iPhone®, iPodTouch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch-sensitive display system 112 optionally has a video resolution inexcess of 100 dpi. In some embodiments, the touch screen videoresolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater).The user optionally makes contact with touch-sensitive display system112 using any suitable object or appendage, such as a stylus, a finger,and so forth. In some embodiments, the user interface is designed towork with finger-based contacts and gestures, which can be less precisethan stylus-based input due to the larger area of contact of a finger onthe touch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch-sensitive displaysystem 112 or an extension of the touch-sensitive surface formed by thetouch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled with optical sensor controller158 in I/O subsystem 106. Optical sensor(s) 164 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 164 receive light from theenvironment, projected through one or more lens, and convert the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor(s) 164 optionally capturestill images and/or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch-sensitive displaysystem 112 on the front of the device, so that the touch screen isenabled for use as a viewfinder for still and/or video imageacquisition. In some embodiments, another optical sensor is located onthe front of the device so that the user's image is obtained (e.g., forselfies, for videoconferencing while the user views the other videoconference participants on the touch screen, etc.).

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled withintensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor(s) 165 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a touch-sensitive surface). Contactintensity sensor(s) 165 receive contact intensity information (e.g.,pressure information or a proxy for pressure information) from theenvironment. In some embodiments, at least one contact intensity sensoris collocated with, or proximate to, a touch-sensitive surface (e.g.,touch-sensitive display system 112). In some embodiments, at least onecontact intensity sensor is located on the back of device 100, oppositetouch-screen display system 112 which is located on the front of device100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled with peripherals interface118. Alternately, proximity sensor 166 is coupled with input controller160 in I/O subsystem 106. In some embodiments, the proximity sensorturns off and disables touch-sensitive display system 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled withhaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator(s) 167 optionally include one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Tactile output generator(s) 167 receive tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch-sensitive display system 112, which islocated on the front of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled with peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled with an inputcontroller 160 in I/O subsystem 106. In some embodiments, information isdisplayed on the touch-screen display in a portrait view or a landscapeview based on an analysis of data received from the one or moreaccelerometers. Device 100 optionally includes, in addition toaccelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASSor other global navigation system) receiver (not shown) for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, haptic feedback module (orset of instructions) 133, text input module (or set of instructions)134, Global Positioning System (GPS) module (or set of instructions)135, and applications (or sets of instructions) 136. Furthermore, insome embodiments, memory 102 stores device/global internal state 157, asshown in FIGS. 1A and 3. Device/global internal state 157 includes oneor more of: active application state, indicating which applications, ifany, are currently active; display state, indicating what applications,views or other information occupy various regions of touch-sensitivedisplay system 112; sensor state, including information obtained fromthe device's various sensors and other input or control devices 116; andlocation and/or positional information concerning the device's locationand/or attitude.

Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used in some iPhone®, iPod Touch®, and iPad® devicesfrom Apple Inc. of Cupertino, Calif. In some embodiments, the externalport is a Lightning connector that is the same as, or similar to and/orcompatible with the Lightning connector used in some iPhone®, iPodTouch®, and iPad® devices from Apple Inc. of Cupertino, Calif.

Contact/motion module 130 optionally detects contact withtouch-sensitive display system 112 (in conjunction with displaycontroller 156) and other touch-sensitive devices (e.g., a touchpad orphysical click wheel). Contact/motion module 130 includes varioussoftware components for performing various operations related todetection of contact (e.g., by a finger or by a stylus), such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts or stylus contacts) or to multiplesimultaneous contacts (e.g., “multitouch”/multiple finger contacts). Insome embodiments, contact/motion module 130 and display controller 156detect contact on a touchpad.

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event. Similarly, tap,swipe, drag, and other gestures are optionally detected for a stylus bydetecting a particular contact pattern for the stylus.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch-sensitive display system 112or other display, including components for changing the visual impact(e.g., brightness, transparency, saturation, contrast or other visualproperty) of graphics that are displayed. As used herein, the term“graphics” includes any object that can be displayed to a user,including without limitation text, web pages, icons (such asuser-interface objects including soft keys), digital images, videos,animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, contacts module 137 includes executable instructions tomanage an address book or contact list (e.g., stored in applicationinternal state 192 of contacts module 137 in memory 102 or memory 370),including: adding name(s) to the address book; deleting name(s) from theaddress book; associating telephone number(s), e-mail address(es),physical address(es) or other information with a name; associating animage with a name; categorizing and sorting names; providing telephonenumbers and/or e-mail addresses to initiate and/or facilitatecommunications by telephone 138, video conference 139, e-mail 140, or IM141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, contact module 130, graphics module 132, and text input module 134,telephone module 138 includes executable instructions to enter asequence of characters corresponding to a telephone number, access oneor more telephone numbers in address book 137, modify a telephone numberthat has been entered, dial a respective telephone number, conduct aconversation and disconnect or hang up when the conversation iscompleted. As noted above, the wireless communication optionally usesany of a plurality of communications standards, protocols andtechnologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, optical sensor(s) 164, optical sensor controller 158, contactmodule 130, graphics module 132, text input module 134, contact list137, and telephone module 138, videoconferencing module 139 includesexecutable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants inaccordance with user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, the instant messaging module 141 includesexecutable instructions to enter a sequence of characters correspondingto an instant message, to modify previously entered characters, totransmit a respective instant message (for example, using a ShortMessage Service (SMS) or Multimedia Message Service (MIMS) protocol fortelephony-based instant messages or using XMPP, SIMPLE, Apple PushNotification Service (APNs) or IMPS for Internet-based instantmessages), to receive instant messages and to view received instantmessages. In some embodiments, transmitted and/or received instantmessages optionally include graphics, photos, audio files, video filesand/or other attachments as are supported in a MIMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MIMS)and Internet-based messages (e.g., messages sent using XMPP, SIMPLE,APNs, or IMPS).

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,text input module 134, GPS module 135, map module 154, and music playermodule 146, workout support module 142 includes executable instructionsto create workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (in sports devices and smartwatches); receive workout sensor data; calibrate sensors used to monitora workout; select and play music for a workout; and display, store andtransmit workout data.

In conjunction with touch-sensitive display system 112, displaycontroller 156, optical sensor(s) 164, optical sensor controller 158,contact module 130, graphics module 132, and image management module144, camera module 143 includes executable instructions to capture stillimages or video (including a video stream) and store them into memory102, modify characteristics of a still image or video, and/or delete astill image or video from memory 102.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, and camera module 143, image management module 144 includesexecutable instructions to arrange, modify (e.g., edit), or otherwisemanipulate, label, delete, present (e.g., in a digital slide show oralbum), and store still and/or video images.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, and text input module 134, browser module 147 includes executableinstructions to browse the Internet in accordance with userinstructions, including searching, linking to, receiving, and displayingweb pages or portions thereof, as well as attachments and other fileslinked to web pages.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, e-mail client module 140, and browser module147, calendar module 148 includes executable instructions to create,display, modify, and store calendars and data associated with calendars(e.g., calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, widget modules 149are mini-applications that are, optionally, downloaded and used by auser (e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, the widget creatormodule 150 includes executable instructions to create widgets (e.g.,turning a user-specified portion of a web page into a widget).

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, search module 151 includes executable instructions to searchfor text, music, sound, image, video, and/or other files in memory 102that match one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, and browser module 147, video andmusic player module 152 includes executable instructions that allow theuser to download and play back recorded music and other sound filesstored in one or more file formats, such as MP3 or AAC files, andexecutable instructions to display, present or otherwise play backvideos (e.g., on touch-sensitive display system 112, or on an externaldisplay connected wirelessly or via external port 124). In someembodiments, device 100 optionally includes the functionality of an MP3player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, notes module 153 includes executable instructions to createand manage notes, to do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, GPS module 135, and browser module 147, mapmodule 154 includes executable instructions to receive, display, modify,and store maps and data associated with maps (e.g., driving directions;data on stores and other points of interest at or near a particularlocation; and other location-based data) in accordance with userinstructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesexecutable instructions that allow the user to access, browse, receive(e.g., by streaming and/or download), play back (e.g., on the touchscreen 112, or on an external display connected wirelessly or viaexternal port 124), send an e-mail with a link to a particular onlinevideo, and otherwise manage online videos in one or more file formats,such as H.264. In some embodiments, instant messaging module 141, ratherthan e-mail client module 140, is used to send a link to a particularonline video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 136, 137-155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay system 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display system 112, as part of amulti-touch gesture). Peripherals interface 118 transmits information itreceives from I/O subsystem 106 or a sensor, such as proximity sensor166, accelerometer(s) 168, and/or microphone 113 (through audiocircuitry 110). Information that peripherals interface 118 receives fromI/O subsystem 106 includes information from touch-sensitive displaysystem 112 or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch-sensitive display system 112 displays more than one view.Views are made up of controls and other elements that a user can see onthe display.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177 or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay system 112, and lift-off of the touch (touch end). In someembodiments, the event also includes information for one or moreassociated event handlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display system 112, when a touch is detected ontouch-sensitive display system 112, event comparator 184 performs a hittest to determine which of the three user-interface objects isassociated with the touch (sub-event). If each displayed object isassociated with a respective event handler 190, the event comparatoruses the result of the hit test to determine which event handler 190should be activated. For example, event comparator 184 selects an eventhandler associated with the sub-event and the object triggering the hittest.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A) in accordancewith some embodiments. The touch screen optionally displays one or moregraphics within user interface (UI) 200. In this embodiment, as well asothers described below, a user is enabled to select one or more of thegraphics by making a gesture on the graphics, for example, with one ormore fingers 202 (not drawn to scale in the figure) or one or morestyluses 203 (not drawn to scale in the figure). In some embodiments,selection of one or more graphics occurs when the user breaks contactwith the one or more graphics. In some embodiments, the gestureoptionally includes one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some implementations orcircumstances, inadvertent contact with a graphic does not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon optionally does not select the corresponding application when thegesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on the touch-screen display.

In some embodiments, device 100 includes the touch-screen display, menubutton 204, push button 206 for powering the device on/off and lockingthe device, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In some embodiments, device 100 also accepts verbalinput for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch-sensitive display system 112 and/or one or more tactile outputgenerators 167 for generating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch-screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that are, optionally, implemented on portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser,” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod,” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages,”        -   Icon 426 for calendar module 148, labeled “Calendar,”        -   Icon 428 for image management module 144, labeled “Photos,”        -   Icon 430 for camera module 143, labeled “Camera,”        -   Icon 432 for online video module 155, labeled “Online            Video,”        -   Icon 434 for stocks widget 149-2, labeled “Stocks,”        -   Icon 436 for map module 154, labeled “Map,”        -   Icon 438 for weather widget 149-1, labeled “Weather,”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock,”        -   Icon 442 for workout support module 142, labeled “Workout            Support,”        -   Icon 444 for notes module 153, labeled “Notes,” and        -   Icon 446 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, in some embodiments, icon 422 for videoand music player module 152 is labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450. Device300 also, optionally, includes one or more contact intensity sensors(e.g., one or more of sensors 359) for detecting intensity of contactson touch-sensitive surface 451 and/or one or more tactile outputgenerators 357 for generating tactile outputs for a user of device 300.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450. Althoughmany of the examples that follow will be given with reference to inputson touch screen display 112 (where the touch sensitive surface and thedisplay are combined), in some embodiments, the device detects inputs ona touch-sensitive surface that is separate from the display, as shown inFIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 inFIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) that corresponds to aprimary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). Inaccordance with these embodiments, the device detects contacts (e.g.,460 and 462 in FIG. 4B) with the touch-sensitive surface 451 atlocations that correspond to respective locations on the display (e.g.,in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In thisway, user inputs (e.g., contacts 460 and 462, and movements thereof)detected by the device on the touch-sensitive surface (e.g., 451 in FIG.4B) are used by the device to manipulate the user interface on thedisplay (e.g., 450 in FIG. 4B) of the multifunction device when thetouch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures, etc.), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or a stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or the touch screenin FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact or a styluscontact) on the touch-sensitive surface, or to a substitute (proxy) forthe force or pressure of a contact on the touch-sensitive surface. Theintensity of a contact has a range of values that includes at least fourdistinct values and more typically includes hundreds of distinct values(e.g., at least 256). Intensity of a contact is, optionally, determined(or measured) using various approaches and various sensors orcombinations of sensors. For example, one or more force sensorsunderneath or adjacent to the touch-sensitive surface are, optionally,used to measure force at various points on the touch-sensitive surface.In some implementations, force measurements from multiple force sensorsare combined (e.g., a weighted average or a sum) to determine anestimated force of a contact. Similarly, a pressure-sensitive tip of astylus is, optionally, used to determine a pressure of the stylus on thetouch-sensitive surface. Alternatively, the size of the contact areadetected on the touch-sensitive surface and/or changes thereto, thecapacitance of the touch-sensitive surface proximate to the contactand/or changes thereto, and/or the resistance of the touch-sensitivesurface proximate to the contact and/or changes thereto are, optionally,used as a substitute for the force or pressure of the contact on thetouch-sensitive surface. In some implementations, the substitutemeasurements for contact force or pressure are used directly todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is described in units corresponding to thesubstitute measurements). In some implementations, the substitutemeasurements for contact force or pressure are converted to an estimatedforce or pressure and the estimated force or pressure is used todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is a pressure threshold measured in units ofpressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be readily accessible by the user on a reduced-size devicewith limited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch-screen display can be set to any of alarge range of predefined thresholds values without changing thetrackpad or touch-screen display hardware. Additionally, in someimplementations a user of the device is provided with software settingsfor adjusting one or more of the set of intensity thresholds (e.g., byadjusting individual intensity thresholds and/or by adjusting aplurality of intensity thresholds at once with a system-level click“intensity” parameter).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second intensity threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more intensity thresholds is used to determine whether or not toperform one or more operations (e.g., whether to perform a respectiveoption or forgo performing the respective operation) rather than beingused to determine whether to perform a first operation or a secondoperation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location (e.g.,a drag gesture), at which point the intensity of the contact increases.In this example, the characteristic intensity of the contact at the endlocation may be based on only a portion of the continuous swipe contact,and not the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmmay be applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The user interface figures described herein optionally include variousintensity diagrams that show the current intensity of the contact on thetouch-sensitive surface relative to one or more intensity thresholds(e.g., a contact detection intensity threshold IT₀, a light pressintensity threshold IT_(L), a deep press intensity threshold IT_(D)(e.g., that is at least initially higher than I_(L)), and/or one or moreother intensity thresholds (e.g., an intensity threshold I_(H) that islower than I_(L))). This intensity diagram is typically not part of thedisplayed user interface, but is provided to aid in the interpretationof the figures. In some embodiments, the light press intensity thresholdcorresponds to an intensity at which the device will perform operationstypically associated with clicking a button of a physical mouse or atrackpad. In some embodiments, the deep press intensity thresholdcorresponds to an intensity at which the device will perform operationsthat are different from operations typically associated with clicking abutton of a physical mouse or a trackpad. In some embodiments, when acontact is detected with a characteristic intensity below the lightpress intensity threshold (e.g., and above a nominal contact-detectionintensity threshold IT₀ below which the contact is no longer detected),the device will move a focus selector in accordance with movement of thecontact on the touch-sensitive surface without performing an operationassociated with the light press intensity threshold or the deep pressintensity threshold. Generally, unless otherwise stated, these intensitythresholds are consistent between different sets of user interfacefigures.

In some embodiments, the response of the device to inputs detected bythe device depends on criteria based on the contact intensity during theinput. For example, for some “light press” inputs, the intensity of acontact exceeding a first intensity threshold during the input triggersa first response. In some embodiments, the response of the device toinputs detected by the device depends on criteria that include both thecontact intensity during the input and time-based criteria. For example,for some “deep press” inputs, the intensity of a contact exceeding asecond intensity threshold during the input, greater than the firstintensity threshold for a light press, triggers a second response onlyif a delay time has elapsed between meeting the first intensitythreshold and meeting the second intensity threshold. This delay time istypically less than 200 ms in duration (e.g., 40, 100, or 120 ms,depending on the magnitude of the second intensity threshold, with thedelay time increasing as the second intensity threshold increases). Thisdelay time helps to avoid accidental deep press inputs. As anotherexample, for some “deep press” inputs, there is a reduced-sensitivitytime period that occurs after the time at which the first intensitythreshold is met. During the reduced-sensitivity time period, the secondintensity threshold is increased. This temporary increase in the secondintensity threshold also helps to avoid accidental deep press inputs.For other deep press inputs, the response to detection of a deep pressinput does not depend on time-based criteria.

In some embodiments, one or more of the input intensity thresholdsand/or the corresponding outputs vary based on one or more factors, suchas user settings, contact motion, input timing, application running,rate at which the intensity is applied, number of concurrent inputs,user history, environmental factors (e.g., ambient noise), focusselector position, and the like. Exemplary factors are described in U.S.patent application Ser. Nos. 14/399,606 and 14/624,296, which areincorporated by reference herein in their entireties.

For example, FIG. 4C illustrates a dynamic intensity threshold 480 thatchanges over time based in part on the intensity of touch input 476 overtime. Dynamic intensity threshold 480 is a sum of two components, firstcomponent 474 that decays over time after a predefined delay time p1from when touch input 476 is initially detected, and second component478 that trails the intensity of touch input 476 over time. The initialhigh intensity threshold of first component 474 reduces accidentaltriggering of a “deep press” response, while still allowing an immediate“deep press” response if touch input 476 provides sufficient intensity.Second component 478 reduces unintentional triggering of a “deep press”response by gradual intensity fluctuations of in a touch input. In someembodiments, when touch input 476 satisfies dynamic intensity threshold480 (e.g., at point 481 in FIG. 4C), the “deep press” response istriggered.

FIG. 4D illustrates another dynamic intensity threshold 486 (e.g.,intensity threshold I_(D)). FIG. 4D also illustrates two other intensitythresholds: a first intensity threshold I_(H) and a second intensitythreshold I_(L). In FIG. 4D, although touch input 484 satisfies thefirst intensity threshold I_(H) and the second intensity threshold I_(L)prior to time p2, no response is provided until delay time p2 haselapsed at time 482. Also in FIG. 4D, dynamic intensity threshold 486decays over time, with the decay starting at time 488 after a predefineddelay time p1 has elapsed from time 482 (when the response associatedwith the second intensity threshold I_(L) was triggered). This type ofdynamic intensity threshold reduces accidental triggering of a responseassociated with the dynamic intensity threshold I_(D) immediately after,or concurrently with, triggering a response associated with a lowerintensity threshold, such as the first intensity threshold I_(H) or thesecond intensity threshold I_(L).

FIG. 4E illustrate yet another dynamic intensity threshold 492 (e.g.,intensity threshold I_(D)). In FIG. 4E, a response associated with theintensity threshold I_(L) is triggered after the delay time p2 haselapsed from when touch input 490 is initially detected. Concurrently,dynamic intensity threshold 492 decays after the predefined delay timep1 has elapsed from when touch input 490 is initially detected. So adecrease in intensity of touch input 490 after triggering the responseassociated with the intensity threshold I_(L), followed by an increasein the intensity of touch input 490, without releasing touch input 490,can trigger a response associated with the intensity threshold I_(D)(e.g., at time 494) even when the intensity of touch input 490 is belowanother intensity threshold, for example, the intensity threshold I_(L).

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold IT_(L) to an intensity betweenthe light press intensity threshold IT_(L) and the deep press intensitythreshold IT_(D) is sometimes referred to as a “light press” input. Anincrease of characteristic intensity of the contact from an intensitybelow the deep press intensity threshold IT_(D) to an intensity abovethe deep press intensity threshold IT_(D) is sometimes referred to as a“deep press” input. An increase of characteristic intensity of thecontact from an intensity below the contact-detection intensitythreshold IT₀ to an intensity between the contact-detection intensitythreshold IT₀ and the light press intensity threshold IT_(L) issometimes referred to as detecting the contact on the touch-surface. Adecrease of characteristic intensity of the contact from an intensityabove the contact-detection intensity threshold IT₀ to an intensitybelow the contact-detection intensity threshold IT₀ is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments IT₀ is zero. In some embodiments, IT₀ is greaterthan zero. In some illustrations a shaded circle or oval is used torepresent intensity of a contact on the touch-sensitive surface. In someillustrations, a circle or oval without shading is used represent arespective contact on the touch-sensitive surface without specifying theintensity of the respective contact.

In some embodiments, described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., the respective operation is performed on a“down stroke” of the respective press input). In some embodiments, thepress input includes an increase in intensity of the respective contactabove the press-input intensity threshold and a subsequent decrease inintensity of the contact below the press-input intensity threshold, andthe respective operation is performed in response to detecting thesubsequent decrease in intensity of the respective contact below thepress-input threshold (e.g., the respective operation is performed on an“up stroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., the respective operationis performed on an “up stroke” of the respective press input).Similarly, in some embodiments, the press input is detected only whenthe device detects an increase in intensity of the contact from anintensity at or below the hysteresis intensity threshold to an intensityat or above the press-input intensity threshold and, optionally, asubsequent decrease in intensity of the contact to an intensity at orbelow the hysteresis intensity, and the respective operation isperformed in response to detecting the press input (e.g., the increasein intensity of the contact or the decrease in intensity of the contact,depending on the circumstances).

For ease of explanation, the description of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting: an increase in intensityof a contact above the press-input intensity threshold, an increase inintensity of a contact from an intensity below the hysteresis intensitythreshold to an intensity above the press-input intensity threshold, adecrease in intensity of the contact below the press-input intensitythreshold, or a decrease in intensity of the contact below thehysteresis intensity threshold corresponding to the press-inputintensity threshold. Additionally, in examples where an operation isdescribed as being performed in response to detecting a decrease inintensity of a contact below the press-input intensity threshold, theoperation is, optionally, performed in response to detecting a decreasein intensity of the contact below a hysteresis intensity thresholdcorresponding to, and lower than, the press-input intensity threshold.As described above, in some embodiments, the triggering of theseresponses also depends on time-based criteria being met (e.g., a delaytime has elapsed between a first intensity threshold being met and asecond intensity threshold being met).

USER INTERFACES AND ASSOCIATED PROCESSES

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronicdevice, such as portable multifunction device 100 or device 300, with adisplay, a touch-sensitive surface, and one or more sensors to detectintensities of contacts with the touch-sensitive surface.

FIGS. 5A-5I illustrate exemplary user interfaces for displaying anexpanded portion of a slider, in accordance with some embodiments. Theuser interfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIGS. 7A-7D and 8A-8D. Forconvenience of explanation, some of the embodiments will be discussedwith reference to operations performed on a device with atouch-sensitive display system 112. In such embodiments, the focusselector is, optionally: a respective finger or stylus contact, arepresentative point corresponding to a finger or stylus contact (e.g.,a centroid of a respective contact or a point associated with arespective contact), or a centroid of two or more contacts detected onthe touch-sensitive display system 112. However, analogous operationsare, optionally, performed on a device with a display 450 and a separatetouch-sensitive surface 451 in response to detecting the contacts on thetouch-sensitive surface 451 while displaying the user interfaces shownin the figures on the display 450, along with a focus selector.

FIG. 5A illustrates a user interface that includes user interfaceobjects, in accordance with some embodiments. The illustrative userinterface of FIG. 5A includes user interface objects for a mediaplayback application, including a media playback slider 502 and otheruser interface objects: media playback controls (previous track control508, pause control 510, next track control 512), content identificationinformation object 514, and volume slider 516. Media playback slider 502represents an audio track. Lower range value indicator 504 indicates atime value (0:00) of a position in the audio track corresponding to theleft edge of media playback slider 502 and upper range value indicator506 indicates a time value (2:15) of a position in the audio trackcorresponding to the right edge of media playback slider 502. A contactwith touch screen 112 is received at a location indicated by focusselector 518. Focus selector 518 is at a location of play head 520. Playhead 520 is a thumb control for slider 502. As a contact with touchscreen 112 is moved along media playback slider 502 from the locationindicated by focus selector 518, play head 520 is moved in the directionof the contact's movement. In some embodiments, play back of the audiotrack represented by media playback slider 502 is initiated and/orresumed from a position in time indicated by play head 520. Thecharacteristic intensity of the contact is indicated by intensity meter522. In FIG. 5A, the characteristic intensity of the contact (asindicated by intensity meter 522) is between a contact-detectionintensity threshold IT₀ and a hint intensity threshold IT_(H).

FIG. 5B illustrates a user interface in which an expanded portion ofmedia playback slider 502 is displayed, in accordance with someembodiments. In FIG. 5B, the characteristic intensity of the contact atthe location indicated by focus selector 518 has increased to above thehint intensity threshold IT_(H), as indicated by intensity meter 522. Incomparison with media playback slider 502 as shown in FIG. 5A, mediaplayback slider 502 as shown in FIG. 5B is vertically expanded,magnifying the slider to reveal an audio waveform 524 (or to furtherreveal audio waveform 526, if audio waveform 524 was previously visible)corresponding to the audio track represented by media playback slider502. The expanded portion of media playback slider 502 as shown in FIG.5B, with time value 0:15 shown at lower range value indicator 504 andtime value 2:01 shown at upper range value indicator 506, is less thanall of media playback slider 502 as shown in FIG. 5A (in which lowerrange value indicator 504 showed time value 0:00 and upper range valueindicator 506 showed time value 2:15). In FIG. 5B, the appearance ofuser interface objects 508, 510, 512, 514, and 516 is maintained (i.e.,the appearance of user interface objects 508, 510, 512, 514, and 516 isnot changed from the appearance of these user interface objects in FIG.5A) while the expanded portion of media playback slider 502 isdisplayed. Play head 520 remains displayed under focus selector 518 whenthe expanded portion of media playback slider 502 is displayed.

FIG. 5C illustrates a user interface in which a further expanded portionof media playback slider 502 is shown, in accordance with someembodiments. In response to detecting a second increase in thecharacteristic intensity of the contact at the location indicated byfocus selector 518, a further expanded portion of media playback slider502 is displayed. For example, the second increase in the characteristicintensity is an increase from above the hint intensity threshold IT_(H),as shown in FIG. 5B, to above a light press intensity threshold IT_(L),as shown by intensity meter 522 of FIG. 5C. Alternatively, the secondincrease in the characteristic intensity is an increase in thecharacteristic intensity (e.g., an increase to above the hint intensitythreshold IT_(H)) that follows a decrease in characteristic intensity(e.g., a decrease below the hint intensity threshold IT_(H)) subsequentto the first increase in the characteristic intensity (e.g., theincrease above the hint intensity threshold IT_(H) as shown by intensitylevel meter 522 in FIG. 5B). In comparison with media playback slider502, as shown in FIG. 5B, media playback slider 502 as shown in FIG. 5Cis vertically expanded, e.g., magnified to further reveal audio waveform526. The expanded portion of media playback slider 502 as shown in FIG.5C, with time value 0:35 shown by lower range value indicator 504 andtime value 1:41 shown by upper range value indicator 506, is less thanall of media playback slider 502 as shown in FIG. 5B (in which lowerrange value indicator 504 showed time value 0:15 and upper range valueindicator 506 showed time value 2:01). In FIG. 5C, the appearance ofuser interface objects 508, 510, 512, 514, and 516 is maintained (e.g.,the appearance of user interface objects 508, 510, 512, 514, and 516 isnot changed from the appearance of these user interface objects in FIG.5A) while the further expanded portion of media playback slider 502 isdisplayed. Play head 520 remains displayed under focus selector 518 whenthe further expanded portion of media playback slider 502 is displayed.

FIG. 5D illustrates a series of user interfaces 530, 532, 534, 536, and538 a/538 b (which occur at sequential times t₀, t₁, t₂, t₃, and t₄,respectively) in which media playback slider 502 is shown with varyingdegrees of expansion, in accordance with some embodiments.

In user interface 530, a characteristic intensity level of a contact ata location indicated by focus selector 518-0 is between acontact-detection intensity threshold IT₀ and a hint intensity thresholdIT_(H), as indicated by intensity level meter 522-0 shown adjacent touser interface 530. Media playback slider 502-0 of user interface 530 isshown in an initial state.

In user interface 532, the characteristic intensity level of the contactat the location indicated by focus selector 518-1 has increased to aboveIT_(H), as indicated by intensity level meter 522-1 shown adjacent touser interface 532. In response to the increase in the characteristicintensity (from the characteristic intensity indicated by intensitymeter 522-0 shown adjacent to user interface 530), an expanded portionof media playback slider 502-1 is displayed.

In user interface 534, the characteristic intensity of the contact atthe location indicated by focus selector 518-2 has decreased to belowIT_(H), as indicated by intensity meter 522-2 shown adjacent to userinterface 534. In response to the decrease in the characteristicintensity (from the characteristic intensity indicated by intensitymeter 522-1 shown adjacent to user interface 532), the display of theexpanded portion of media playback slider 502-2 is maintained (e.g., thesame expanded portion of media playback slider 502 is shown in userinterface 532 and user interface 534).

In user interface 536, the characteristic intensity of the contact atthe location indicated by focus selector 518-3 has again increased toabove IT_(H), as indicated by intensity meter 522-3 shown adjacent touser interface 536. In response to the second increase in thecharacteristic intensity (from the characteristic intensity indicated byintensity meter 522-2 shown adjacent to user interface 534), a furtherexpanded portion of media playback slider 502-3 is displayed.

Subsequent to displaying user interface 536, a user interface as shownin 538 a is displayed, in accordance with some embodiments. In userinterface 538 a, the contact has lifted off from touch screen 112. Inresponse to the liftoff, media playback slider 502 is displayed at itsinitial state.

Alternatively, subsequent to displaying user interface 536, a userinterface as shown in 538 b is displayed, in accordance with someembodiments. In user interface 538 b, the contact has lifted off fromtouch screen 112. In response to the liftoff, display of the furtherexpanded portion media playback slider 502 is maintained.

FIG. 5E illustrates a first series of user interfaces 540-542 (occurringat sequential times t₀ and t₁) and a second series of user interfaces544-546 (occurring at sequential times t₂ and t₃) in which movement ofthe focus selector 518 along media playback slider 502 occurs, inaccordance with some embodiments. The first series of user interfaces540-542 illustrate user interfaces that occur when intensity criteriaare not met. The second series of user interfaces 544-546 illustrateuser interfaces that occur when intensity criteria are met. In theillustrative example of FIG. 5E, intensity criteria are met when acharacteristic intensity of a contact exceeds an intensity thresholdIT_(H), as indicated by intensity meter 522.

In user interface 540, a contact moves play head 520-0 along mediaplayback slider 502-0 from a first position indicated by focus selector518 a to a second position indicated by focus selector 518 b, asindicated by arrow 548. A characteristic intensity of the contact hasnot met first criteria (e.g. the characteristic intensity of the contacthas not exceeded an intensity threshold IT_(H), during and/or prior tothe movement of the focus selector along media playback slider 502-0).

In user interface 542, the value of the media playback slider 502-2(e.g., the position indicated by play head 520-1) is shifted by a firstamount (e.g., shifted from time value 1:00, at focus selector location518 a of user interface 540, to time value 1:40, at focus selectorlocation 518 b of user interface 542).

In user interface 544, a contact moves play head 520-2 along mediaplayback slider 502-2 from a first position indicated by focus selector518 c to a second position indicated by focus selector 518 d, asindicated by arrow 550. A characteristic intensity of the contact hasmet the first criteria (e.g. the characteristic intensity of the contacthas exceeded the intensity threshold IT_(H), during and/or prior to themovement of the focus selector along media playback slider 502-2).

In user interface 546, the value of the media playback slider 502-3(e.g., the position indicated by play head 520-3) is shifted by a secondamount (e.g., shifted from time value 1:20, at focus selector location518 c of user interface 544, to time value 1:40, at focus selectorlocation 518 d of user interface 546).

FIGS. 5F-5G illustrate expansion of a portion of a volume slider 516, inaccordance with some embodiments.

In FIG. 5F, a contact with touch screen 112 is received at a locationindicated by focus selector 518. Focus selector 518 is at a location ofvolume control 552. Volume control 552 is a thumb control for volumeslider 516. As a contact with touch screen 112 is moved along volumeslider 516 from the location indicated by focus selector 518, volumecontrol 552 is moved in the direction of the contact's movement. In someembodiments, the sound level of media playback is increased or decreasedbased on the position along volume slider 516 indicated by volumecontrol 552. The characteristic intensity of the contact is indicated byintensity meter 522. In FIG. 5F, the characteristic intensity of thecontact (as indicated by intensity meter 522) is between acontact-detection intensity threshold IT₀ and a hint intensity thresholdIT_(H).

FIG. 5G illustrates a user interface in which an expanded portion ofvolume slider 516 is displayed, in accordance with some embodiments. InFIG. 5G, the characteristic intensity of the contact at the locationindicated by focus selector 518 has increased to above the hintintensity threshold IT_(H), as indicated by intensity meter 522. Incomparison with volume slider 516 as shown in FIG. 5F, volume slider 516as shown in FIG. 5G is vertically expanded. In FIG. 5G, the appearanceof user interface objects 502, 504, 506, 508, 510, 512, 514, and 520 ismaintained (e.g., the appearance of user interface objects 502, 504,506, 508, 510, 512, 514, and 520 is not changed from the appearance ofthese user interface objects in FIG. 5F) while the expanded portion ofvolume slider 516 is displayed. Volume control 552 remains displayedunder focus selector 518 when the expanded portion of volume slider 516is displayed.

FIGS. 5H-5I illustrate expansion of a portion of a video timeline slider560, in accordance with some embodiments.

FIG. 5H illustrates a user interface that includes user interfaceobjects, in accordance with some embodiments. The illustrative userinterface of FIG. 5H includes user interface objects for a videoapplication, including video timeline slider 560 and other userinterface objects: video playback window 564; video management tools566, 568, 570, and 572; back button 574, and video identificationinformation object 576. In FIG. 5H, a contact with touch screen 112 isreceived at a location indicated by focus selector 518. Focus selector518 is at a location of video timeline slider 560. Video timeline slider560 is a representation of a video and includes a sequence of eightframes, including frame 562, indicating various locations (e.g., atperiodic intervals) within the video. As a contact with touch screen 112is moved along video timeline slider 560 from the location indicated byfocus selector 518, a playback position within a video represented byvideo timeline slider 560 is adjusted (e.g., set at a location withinthe video indicated by a frame under focus selector 518 or set at alocation within an interval between adjacent frames of video timelinebased on the location of focus selector 518 within a frame). Thecharacteristic intensity of the contact is indicated by intensity meter522. In FIG. 5H, the characteristic intensity of the contact (asindicated by intensity meter 522) is between a contact-detectionintensity threshold IT₀ and a hint intensity threshold IT_(H).

FIG. 5I illustrates a user interface in which an expanded portion ofvideo timeline slider 560 is displayed, in accordance with someembodiments. In FIG. 5I, the characteristic intensity of the contact atthe location indicated by focus selector 518 has increased to above thehint intensity threshold IT_(H), as indicated by intensity meter 522. Incomparison with video timeline slider 560 as shown in FIG. 5H, videotimeline slider 560 as shown in FIG. 5I is expanded. The expandedportion of video timeline slider 560 includes a sequence of four frames.The spans of time between the frames of video timeline slider 560 asshown in FIG. 5H are greater than the spans of time between the framesof video timeline slider 560 as shown in FIG. 5I (for example, themovement of the kite from frame to frame in video timeline slider 560 ofFIG. 5I is less than the movement as shown in video timeline slider 560of FIG. 5H). In FIG. 5I, the appearance of user interface objects 564,566, 568, 570, 572, 574, and 576 is maintained (e.g., the appearance ofuser interface objects 564, 566, 568, 570, 572, 574, and 576 is notchanged from the appearance of these user interface objects in FIG. 5H)while the expanded portion of video timeline slider 560 is displayed.

FIGS. 6A-6S illustrate exemplary user interfaces for adjusting aproperty of a user interface element in accordance with someembodiments. The user interfaces in these figures are used to illustratethe processes described below, including the processes in FIGS. 7A-7Dand 8A-8D. Although some of the examples which follow will be given withreference to inputs on a touch-screen display (where the touch-sensitivesurface and the display are combined), in some embodiments, the devicedetects inputs on a touch-sensitive surface 451 that is separate fromthe display 450, as shown in FIG. 4B.

FIG. 6A illustrates a user interface that includes multiple userinterface elements, in accordance with some embodiments. User interfaceelements of FIG. 6A include image message 602 (also referred to hereinas “image 602”), text messages 604 and 606, messaging controls 610 and612, text entry box 614, back button 616, messaging information objects618 and 620, signal strength indicators 402, time indicator 404, andbattery status indicator 406. A contact with touch screen 112 isdetected at a location indicated by focus selector 624. Focus selector624 is at a location of image 602. The characteristic intensity of thecontact is indicated by intensity meter 622. In FIG. 6A, thecharacteristic intensity of the contact (as indicated by intensity meter622) is between a contact-detection intensity threshold IT₀ and a hintintensity threshold IT_(H).

FIG. 6B illustrates a user interface in which a property of a userinterface element has been adjusted (and an increase in thecharacteristic intensity of a contact does not meet intensity criteria),in accordance with some embodiments. In the illustrative example of FIG.6B, a user interface element that is adjusted is image 602 and theproperty of image 602 that is adjusted is the area/display size of image602. In FIG. 6B, the characteristic intensity of the contact at thelocation indicated by focus selector 624 has increased to an intensitylevel above the hint intensity threshold IT_(H), as indicated byintensity meter 622, from an intensity level below the hint intensitythreshold IT_(H) (e.g., as indicated by intensity meter 622 of FIG. 6A).In comparison with image 602 as shown in FIG. 6A, the area/display sizeof image 602 as shown in FIG. 6B is expanded. In some embodiments, apresentation layout of image 602 is adjusted (e.g., image 602transitions from a message balloon format, as shown in FIG. 6A, to arectangular format, as shown in FIG. 6B). In some embodiments, if anincrease in the characteristic intensity of the contact does not meetintensity criteria (such as intensity criteria including a criterionthat is met when an intensity level increases above the hint intensitythreshold IT_(H)), when a decrease in the characteristic intensity ofthe contact is detected, the property (e.g., the area/display size) ofthe user interface element (e.g., image 602) returns to its previousvalue (e.g., image 602's original state, as shown in FIG. 6A).

FIG. 6C illustrates a user interface in which the property of the userinterface element has been returned to its previous value, in accordancewith some embodiments. The user interface of FIG. 6C is shown, forexample, in response to a determination that an increase in thecharacteristic intensity of a contact (e.g., as described with regard toFIG. 6B) did not meet intensity criteria (e.g., the characteristicintensity of the contact in FIG. 6B did not increase above the hintintensity threshold IT_(H)). In FIG. 6C, the characteristic intensity ofthe contact at the location indicated by focus selector 624 hasdecreased to an intensity level below the hint intensity thresholdIT_(H), as indicated by intensity meter 622. In comparison with image602 as shown in FIG. 6B, the area/display size of image 602 as shown inFIG. 6C is decreased. The area of image 602 as shown in FIG. 6C is thesame as the area of image 602 as shown in FIG. 6A.

FIGS. 6D-6F illustrate user interfaces in which the property of the userinterface element has been adjusted and an increase in thecharacteristic intensity of a contact has met intensity criteria.

In FIG. 6D, the characteristic intensity of the contact at the locationindicated by focus selector 624 has increased to an intensity levelabove a light press intensity threshold IT_(L), as indicated byintensity meter 622 of FIG. 6D, from an intensity level below the lightpress intensity threshold IT_(L) (e.g., as indicated by intensity meter622 of FIG. 6A). In response to the increase in the characteristicintensity of the contact, image 602 is increased from an initial value(e.g., an initial area/display size of image 602 as shown in FIG. 6A) toan expanded area/display size as shown in FIG. 6D.

In some embodiments, as shown in FIGS. 6E-6F, adjusting the property(e.g., increasing the area/display size) of the user interface element(e.g., image 602) includes a “rubber band effect” in which the area ofimage 602 expands beyond a target level of expansion and then returns tothe target level of expansion. For example, the adjustment of thearea/display size of image 602 from an initial area/display size (e.g.the area/display size of image 602 as shown in FIG. 6A) to a targetlevel of expansion (e.g., the area/display size of image 602 as shown inFIG. 6D) includes a first portion in which the area/display size ofimage 602 expands beyond the target level of expansion (e.g., thearea/display size of image 602 expands, as shown in FIG. 6E, to an areathat is larger than the area/display size of image 602 as shown in FIG.6D) followed by a second portion in which the area/display size of image602 decreases to the target level of expansion (e.g., the area/displaysize of image 602 decreases from the level of expansion shown in FIG. 6Eto the target level of expansion shown in FIG. 6F). The area/displaysize of image 602 as shown in FIG. 6F is equal to the area/display sizeof image 602 as shown in FIG. 6D.

In FIG. 6F, the characteristic intensity of the contact at the locationindicated by focus selector 624 has decreased to an intensity levelbelow the light press intensity threshold IT_(L) (e.g., from anintensity level above the light press intensity threshold IT_(L) asindicated at FIG. 6D). Because the characteristic intensity of thecontact met intensity criteria (e.g., the characteristic intensity ofthe contact increased above IT_(L)), in response to the decrease in thecharacteristic intensity of the contact, the area/display size of image602 is maintained at the expanded level reached in FIG. 6D.

FIG. 6G illustrates a user interface in which the property of the userinterface element is reduced from a second value of the property whilethe property is maintained above a first value of the property. In someembodiments, when a property of a user interface element is maintainedabove an initial value in response to a decrease in the characteristicintensity of a contact (e.g., area of image 602 is maintained above aninitial area/display size of image 602), the property is reduced (e.g.,until a subsequent intensity increase is detected). For example, ananimation showing a continuous reduction in the area/display size ofimage 602 from the expanded level shown in FIG. 6F is shown (e.g., toindicate a “deflation” from the expanded level). In some embodiments,when a property of a user interface element is maintained above aninitial value in response to a decrease in the characteristic intensityof a contact, a “rubber band” effect occurs (the area/display size ofimage 602 is briefly reduced from the expanded level and subsequentlyreturns to the expanded level). FIG. 6G illustrates a user interface inwhich the area/display size of image 602 is reduced to below theexpanded level shown in FIG. 6F, while the area of image 602 ismaintained above an initial area (e.g., the area/display size of image602 as shown in FIG. 6A).

FIGS. 6H-6J illustrate user interfaces in which the property of the userinterface element has been further adjusted in response to a secondincrease in the characteristic intensity of the contact.

In FIG. 6H, the characteristic intensity of the contact at the locationindicated by focus selector 624 has increased to an intensity levelabove the light press intensity threshold IT_(L), as indicated byintensity meter 622 of FIG. 6H, after a previous increase in thecharacteristic intensity of the contact has been detected (e.g., anincrease from an intensity level as indicated by intensity meter 622 inFIG. 6A to an intensity level as indicated by intensity meter 622 inFIG. 6D), and after a decrease in the characteristic intensity of thecontact has been detected (e.g., as described with regard to FIGS.6D-6G). In response to the second increase in the characteristicintensity of the contact, the area/display size of image 602 is furtherincreased (e.g., beyond the increase in the area/display size of image602 from the initial area as indicated in FIG. 6A to the expanded areaas indicated in FIG. 6D).

FIGS. 6I-6J illustrate a “rubber band” effect in which the area/displaysize of image 602 expands beyond a further expanded area/display sizeand then returns to the further expanded area/display size. For example,the adjustment of the area/display size of image 602 from an expandedarea/display size (e.g. the area/display size of image 602 as shown inFIG. 6D) to a further expanded area (e.g., the area/display size ofimage 602 as shown in FIG. 6J) includes a first portion in which thearea/display size of image 602 expands beyond the further expandedarea/display size (e.g., in FIG. 6I, the area/display size of image 602expands to an area/display size that is larger than the further expandedarea/display size of image 602 as shown in FIG. 6H) followed by a secondportion in which the area/display size of image 602 decreases to thefurther expanded area (e.g., the area/display size of image 602decreases from the level of expansion shown in FIG. 6I to the level ofexpansion shown in FIG. 6J). The area/display size of image 602 as shownin FIG. 6J is equal to the area/display size of image 602 as shown inFIG. 6H.

FIGS. 6K-6M illustrate user interfaces in which the property of the userinterface element has been returned to an initial value in response toliftoff of the contact from touch screen 112.

In FIG. 6K, the contact has lifted off of touch screen 112. In responseto detecting liftoff of the contact, the area/display size of image 602is decreased (e.g., from an area/display size of image 602 as shown inFIG. 6J to an area/display size that is equal to the area/display sizeof image 602 as shown in FIG. 6A).

FIGS. 6L-6M illustrate a “rubber band” effect in which the area/displaysize of image 602 decreases below an initial area/display size of image602 and then bounces back to the initial area/display size. For example,returning the area/display size of image 602 from an expandedarea/display size (e.g. the expanded area/display size of image 602 asshown in FIG. 6F, or the further expanded area/display size of image 602as shown in FIG. 6J) to an initial area/display size (e.g., thearea/display size of image 602 as shown in FIG. 6A) includes a firstportion in which the area/display size of image 602 decreases below theinitial area/display size (e.g., the area/display size of image 602decreases from an initial area/display size as shown in FIG. 6K to asmaller area/display size of image 602 as shown in FIG. 6L) followed bya second portion in which the area/display size of image 602 increasesto the initial area/display size (e.g., the area/display size of image602 increases from the level of expansion shown in FIG. 6L to theinitial area/display area of image 602 as shown in FIG. 6M). Thearea/display size of image 602 as shown in FIG. 6K is equal to thearea/display size of image 602 as shown in FIG. 6M.

FIG. 6N illustrates a user interfaces in which the property of the userinterface element has been maintained above an expanded area/displaysize in response to liftoff of the contact from touch screen 112. InFIG. 6N, the contact has lifted off of touch screen 112. In response toliftoff of the contact, the area/display size of image 602 is maintainedat a constant level (e.g., as shown in FIG. 6N, image 602 is shown witha further expanded area/display size that is equal to the area/displaysize of image 602 in FIG. 6J). Alternatively, the area/display size ofimage 602 is reduced (e.g., decreases gradually) below the area/displaysize of image 602 in FIG. 6J while remaining above the area/display sizeof image 602 as shown in FIG. 6D.

FIG. 6O illustrates a user interface in which a magnification propertyof a user interface element is adjusted. In FIG. 6O, the characteristicintensity of the contact at the location indicated by focus selector 624has increased to an intensity level above the hint intensity thresholdIT_(H), as indicated by intensity meter 622, from an intensity levelbelow the hint intensity threshold IT_(H) (e.g., as indicated byintensity meter 622 of FIG. 6A). In comparison with image 602 as shownin FIG. 6A, the level of magnification of image 602 as shown in FIG. 6Ois increased (while the area/display size of image 602 remains thesame). In FIGS. 6A-6N, a magnification level of image 602 is adjustedwhile the area/display size of image 602 is adjusted.

FIG. 6P illustrates a user interface for a digital content managementapplication that includes multiple user interface elements, inaccordance with some embodiments. User interface elements of FIG. 6Pinclude media playback slider 632, lower range value indicator 634,upper range value indicator 636, media playback controls (previous trackcontrol 638, pause control 640, next track control 642), contentidentification information object 644, volume slider 646, signalstrength indicators 402, time indicator 404, and battery statusindicator 406. Media playback slider 632 represents an audio track.Lower range value indicator 634 indicates a time value (0:00) of aposition in the audio track corresponding to the left edge of mediaplayback slider 632 and upper range value indicator 636 indicates a timevalue (2:15) of a position in the audio track corresponding to the rightedge of media playback slider 632. Play progress in the audio trackrepresented by media playback slider 632 has reached time value 1:36, asindicated by the location of play head 650 relative to the time valuesindicated by lower range value indicator 634 and upper range valueindicator 636. In FIG. 6P, a contact with touch screen 112 is detectedat a location indicated by focus selector 624. Focus selector 624 is ata location of media playback slider 632. The characteristic intensity ofthe contact is indicated by intensity meter 622. In FIG. 6P, thecharacteristic intensity of the contact (as indicated by intensity meter622) is between a contact-detection intensity threshold IT₀ and a hintintensity threshold IT_(H).

FIG. 6Q illustrates a user interface in which a play progress propertyof a user interface element is adjusted. In FIG. 6Q, the characteristicintensity of the contact at the location indicated by focus selector 624has increased to an intensity level above the hint intensity thresholdIT_(H), as indicated by intensity meter 622, from an intensity levelbelow the hint intensity threshold IT_(H) (e.g., as indicated byintensity meter 622 of FIG. 6P). In comparison with media playbackslider 632 as shown in FIG. 6P, the play progress in the audio trackrepresented by media playback slider 632 has increased (e.g., reachedtime value 1:46), as indicated by the location of play head 650 relativeto the time values indicated by lower range value indicator 634 andupper range value indicator 636 in FIG. 6Q.

FIG. 6R illustrates a user interface for a digital content managementapplication that includes multiple user interface elements, inaccordance with some embodiments. User interface elements of FIG. 6Rinclude media playback slider 632, lower range value indicator 634,upper range value indicator 636, media playback controls (previous trackcontrol 638, pause control 640, next track control 642), contentidentification information object 644, volume slider 646, signalstrength indicators 402, time indicator 404, and battery statusindicator 406. In FIG. 6R, a contact with touch screen 112 is detectedat a location indicated by focus selector 624. Focus selector 624 is ata location of volume slider 646. A first volume level, as indicated by alocation of volume control 652 in volume slider 646, is at about aquarter of the maximum volume level. The characteristic intensity of thecontact is indicated by intensity meter 622. In FIG. 6R, thecharacteristic intensity of the contact (as indicated by intensity meter622) is between a contact-detection intensity threshold IT₀ and a hintintensity threshold IT_(H).

FIG. 6S illustrates a user interface in which a volume property of auser interface element is adjusted. In FIG. 6S, the characteristicintensity of the contact at the location indicated by focus selector 624has increased to an intensity level above the light press intensitythreshold IT_(H), as indicated by intensity meter 622, from an intensitylevel below the light press intensity threshold IT_(H) (e.g., asindicated by intensity meter 622 of FIG. 6R). In comparison with volumeslider 646 as shown in FIG. 6R, the volume level as shown in FIG. 6S,has increased (e.g., is at about half of the maximum volume level), asindicated by a location of volume control 652 in volume slider 646 inFIG. 6S.

FIGS. 7A-7D are flow diagrams illustrating a method 700 of displaying anexpanded portion of a slider, in accordance with some embodiments. Themethod 700 is performed at an electronic device (e.g., device 300, FIG.3, or portable multifunction device 100, FIG. 1A) with a display, atouch-sensitive surface, and one or more sensors to detect intensity ofcontacts with the touch-sensitive surface. In some embodiments, thedisplay is a touch-screen display and the touch-sensitive surface is onor integrated with the display. In some embodiments, the display isseparate from the touch-sensitive surface. Some operations in method 700are, optionally, combined and/or the order of some operations is,optionally, changed.

As described below, the method 700 provides an intuitive way to displayan expanded portion of a slider. The method reduces the number, extent,and/or nature of the inputs from a user when displaying an expandedportion of a slider, thereby creating a more efficient human-machineinterface. For battery-operated electronic devices, enabling a user todisplay an expanded portion of a slider faster and more efficientlyconserves power and increases the time between battery charges.

The device (702) displays a user interface that includes a slider thatcorresponds to a first range of values and one or more other userinterface objects (e.g., controls). Exemplary sliders include, withoutlimitation, media playback slider 502, video timeline slider 560, andother progress bars for scrubbing through content (e.g. audio, video, orimage gallery); volume slider 516; slider controls for brightnessadjustment, orientation adjustment (e.g., adjustment of an image inimage editor, an object in a document, etc.), and zoom/magnificationadjustment; and a scroll bar for navigating through a document or set ofdocuments. A first range of values is, e.g., a range of time valuescorresponding to all or part of an audio track (such as time valuesindicated by lower range value indicator 504 and upper range valueindicator 506). Further examples of a range of values include a range ofsound level values, a range of brightness values, and a range of sizevalues. In some embodiments, the other user interface objects (e.g.,user interface objects other than the slider) are associated with thesame functionality as the slider. For example, previous track control508, play/pause control 510, and next track control 512 are othercontrols associated with the functionality of media playback slider 502for scrubbing through media content. In another example, other controlsassociated with the functionality of a brightness slider includecontrols for enabling/disabling communication channels (such as Wi-Fiand Bluetooth) a flashlight control, a control for airport mode, acontrol for locking screen orientation, and a sleep mode control (e.g.,the other controls in a control center screen).

The device detects (704) a contact on the touch-sensitive surface 112while a focus selector 518 is at the slider (e.g., media playback slider502).

In some embodiments, initial detection of the contact on thetouch-sensitive surface occurs (706) when the focus selector 518 is at alocation of a displayed play head in the slider (e.g., play head 520 inmedia playback slider 502).

The device detects (708) (e.g., with the one or more sensors configuredto detect intensity of contacts on the touch-sensitive surface) a firstincrease in a characteristic intensity of the contact on thetouch-sensitive surface 112 while the focus selector 518 is at theslider (e.g., media playback slider 502). For example, in userinterfaces 530-532 of FIG. 5D, a contact occurs at the locationindicated by focus selector 518-1/518-2 at media playback slider502-0/502-1. A characteristic intensity of the contact increases frombelow IT_(H), as indicated at intensity level meter 522 shown adjacentto user interface 530, to above IT_(H), as indicated at intensity levelmeter 522 shown adjacent to user interface 532.

In response to detecting the first increase in the characteristicintensity of the contact on the touch-sensitive surface 112 and inaccordance with a determination that the characteristic intensity of thecontact meets intensity criteria, the device displays (710) an expandedportion, less than all, of the slider (e.g., media playback slider 502)while maintaining an appearance of the one or more other user interfaceobjects (e.g., user interface objects 508, 510, 512, 514, and 516). Insome embodiments, the intensity criteria include a criterion that is metwhen a characteristic intensity of the contact (as indicated byintensity meter 522) increases above a first threshold, such as above ahint intensity threshold IT_(H), or above another static or dynamicallydetermined preview intensity threshold. For example, in FIG. 5D, whenthe characteristic intensity of the contact increases above IT_(H) whilefocus selector 518-1 is at media playback slider 502-1, as shown at userinterface 532, an expanded portion of media playback slider 502-1 isshown. In some embodiments, displaying an expanded portion includesexpanding a vertical dimension of a slider (e.g., vertically expandingan audio waveform as shown at user interface 532), expanding ahorizontal dimension of the slider (e.g., horizontally expanding theslider to widen its width), expanding both a vertical dimension and ahorizontal dimension of the slider. In some embodiments, expansionresults in replacing display of a document (e.g., a book) with a sectionof the document (the section is, e.g., a chapter or a page). In someembodiments, liftoff of the contact from touch screen 112 returns theslider to its pre-expanded state (e.g., as shown in user interface 538 ain FIG. 5D).

In some embodiments, displaying an expanded portion of the sliderincludes modifying (712) range indicator values (e.g., time markers foraudio/video, document section titles/markers, numerical representationsof volume, brightness, angle, etc.) that are displayed on or adjacent tothe slider. For example, the time values indicated by lower range valueindicator 504 and upper range value indicator 506 are modified whenmedia playback slider 502 is expanded from an initial state, as shown inFIG. 5A, to an expanded state, as shown in FIG. 5B, and to a furtherexpanded state, as shown in FIG. 5C.

In some embodiments, in response to detecting the first increase in thecharacteristic intensity of the contact on the touch-sensitive surfaceand in accordance with a determination that the characteristic intensityof the contact does not meet the first intensity criteria (e.g., thecharacteristic intensity of the contact does not increase above IT_(H)),the device maintains (714) the appearance of the slider and the one ormore other controls without displaying an expanded portion of theslider.

In some embodiments, the device detects (716) movement of the focus 518selector along the slider (e.g., media playback slider 502). In responseto detecting movement of the focus selector 518 along the slider: inaccordance with a determination that the first intensity criteria weremet (e.g., a characteristic intensity of the contact increased above anintensity threshold, such as IT_(H)), the device shifts a current valueof the slider by a first amount, and in accordance with a determinationthat the first intensity criteria were not met, the device shifts acurrent value of the slider by a second amount different from the firstamount. For example, a gesture along a progress indicator that is notexpanded (e.g., because the characteristic intensity of the contact didnot meet the first intensity criteria) results in a larger adjustmentrelative to the same distance of gesture along a progress indicator thatis expanded.

In an illustrative example, as shown in user interfaces 540-542 of FIG.5E, focus selector 518 moves along media playback slider 502-0 from afirst position 518 a to a second position 518 b, as indicated by arrow548. In accordance with a determination that the characteristicintensity of the contact did not increase above an intensity thresholdIT_(H) (e.g., while the contact moved along media playback slider 502-0and/or prior to movement of the contact along media playback slider502-0), the current value of the slider (e.g., as indicated by play head520-0) is shifted by a first amount (e.g., shifted from time value 1:00,at focus selector location 518 a of user interface 540, to time value1:40, at focus selector location 518 b of user interface 542). As shownin user interfaces 544-546 of FIG. 5E, focus selector 518 moves alongmedia playback slider 502-2 from a first position 518 c to a secondposition 518 d, as indicated by arrow 550. In accordance with adetermination that the characteristic intensity of the contact increasedabove an intensity threshold (e.g., while the contact moved along mediaplayback slider 502-2 and/or prior to movement of the contact alongmedia playback slider 502-2), the current value of the slider (e.g., asindicated by play head 520-2) is shifted by a second amount (e.g.,shifted from time value 1:20, at focus selector location 518 c of userinterface 544, to time value 1:40, at focus selector location 518 d ofuser interface 546).

In some embodiments, a thumb control (e.g., play head 520, volumecontrol 552, or other sliding control for selecting value along slider)for the slider (e.g. media playback slider 502, volume slider 516, oranother slider) remains displayed (718) under the focus selector whenthe expanded portion of the slider is displayed. For example, play head520 remains displayed under focus selector 518 when an expanded portionof media playback slider 502 is displayed, as shown in FIG. 5B. In someembodiments, the width of the slider expands to the left and to theright so that the thumb control remains centered under the slider.

In some embodiments, after expanding the slider, the device detects(720) a first decrease in the characteristic intensity of the contact onthe touch-sensitive surface while the focus selector is at the slider.For example, in FIG. 5D, a characteristic intensity of the contactdecreases from above an intensity threshold IT_(H), as indicated byintensity meter 522-1 adjacent to user interface 532, to below IT_(H),as indicated by intensity meter 522-2 adjacent to user interface 534. Inresponse to detecting the first decrease in the characteristic intensityof the contact, the device maintains (722) display of the expandedportion of the slider (e.g., at the same level of expansion). Forexample, in FIG. 5D, user interface 534 shows the same expanded portionof media playback slider 502-2 as is shown in media playback slider502-1 of user interface 532. After detecting the decrease in thecharacteristic intensity of the contact and while the expanded portionof the slider is displayed, the device detects (724) a second increasein the characteristic intensity of the contact on the touch-sensitivesurface while the focus selector is at the slider. The second increasein the characteristic intensity of the contact is an increase below,equal to, or above the first increase in the characteristic intensity ofthe contact (e.g., an increase to above IT_(H), an increase to aboveIT_(L), or an increase to another intensity level). For example, in FIG.5D, after the decrease in the characteristic intensity of the contact asshown in user interfaces 532-534, the characteristic intensity increasesfrom below intensity threshold IT_(H), as indicated by intensity meter522-2 adjacent to user interface 534, to above IT_(H), as indicatedintensity meter 522-3 shown adjacent to user interface 536. In responseto detecting the second increase in the characteristic intensity of thecontact, the device displays (726) a further expanded portion of theslider. For example, in FIG. 5D, in response to detecting the secondincrease in the characteristic intensity of the contact as shown in userinterfaces 534-536, user interface 536 displays a further increasedmedia playback slider 502-3. In some embodiments, liftoff of the contactreturns the slider to its pre-expanded state (e.g., as shown in userinterface 538 a of FIG. 5D). In some embodiments, the slider maintainsits current state of expansion on liftoff of the contact (e.g., as shownin user interface 538 b, presented when a contact is lifted off whileuser interface 536 is displayed). In some embodiments, an amount ofexpansion of the portion of the slider is determined by an amount and/orspeed of change of intensity of the contact.

In some embodiments, after expanding the slider, the device detects(728) a first decrease in the characteristic intensity of the contact onthe touch-sensitive surface while the focus selector is at the slider.In response to detecting the first decrease in the characteristicintensity of the contact, the device displays (730) the slider withreduced expansion. In some embodiments, in response to detecting thefirst decrease in the characteristic intensity of the contact, thedisplayed slider is returned to its initial state (e.g., the slider isdisplayed with no expansion).

In some embodiments, a magnification within the expanded portion of theslider increases (732) as the characteristic intensity of the contactincreases.

In some embodiments, the slider is a progress indicator (734) for mediacontent (e.g., a progress indicator for an audio track, such as mediaplayback slider 502; a progress indicator for video content, such asvideo timeline slider 560, or another progress indicator), the firstrange of values includes a first sequence of frames (e.g., a sequence offrames 560 including frame 562 as shown in FIG. 5H) of the media content(e.g., video), and displaying an expanded portion of the slider (e.g.,video timeline slider 560) includes displaying a second sequence offrames of the media content, wherein spans of time between frames of thefirst sequence of frames of the media content are greater than spans oftime between frames of the second sequence of video frames of the mediacontent. For example, the span of time between the first frame and thesecond frame of video timeline slider 560 as shown in FIG. 5H is greaterthan the span of time between the first frame and the second frame ofthe expanded portion of video timeline slider 560 as shown in FIG. 5I.

In some embodiments, while detecting the first increase in thecharacteristic intensity of the contact on the touch-sensitive surface112, the device provides (736), by the touch-sensitive surface 112,tactile output. For example, the tactile output may include a hapticdetent, which may occur, for example, when first intensity criteria aremet, when the characteristic intensity of the contact increases aboveone or more intensity thresholds (e.g., IT_(H), IT_(L), or IT_(D), asindicated by intensity meter 522, or above another static or dynamicallydetermined intensity threshold), periodically as intensity increases,and/or on lateral movement of the contact across touch screen 112 (e.g.,movement of a contact as indicated in user interfaces 540-542 and/or asindicated in user interfaces 544-546 of FIG. 5E). In some embodiments,tactile output is also provided during a first decrease in thecharacteristic intensity, during a second increase in the characteristicintensity, and/or during a subsequent increase or decrease in intensity.

In some embodiments, the tactile output occurs (738) in response todetecting that a current value (e.g., as indicated by a thumb control aprogress indicator, or other contact on the slider, such volume control552 on volume slider 516, play head 520 on media playback slider 502, ora contact on video timeline slider 560) of the slider has changed to apredefined reference value within the slider in response to user input.A predefined reference value is, e.g., a reference value that is definedfor a slider, such as a chapter, track, or track subdivision boundary ina document, audio content, or video content; lx zoom for an image; 90degree rotation of an image or object; or a horizon lock rotation valuefor a photo. For example, as a contact moves across video timelineslider 560, tactile output occurs each time a boundary of a respectiveframe 562 is crossed. In another example, as play head 520 moves acrossmedia playback slider 502, tactile output occurs each time a boundary ofa track subdivision is crossed. In some embodiments, a tactile output isgenerated in response to determining that the current value of theslider has changed away from the predefined reference value in responseto user input (e.g., when the thumb control or progress indicator movesaway from the predefined reference value). In some embodiments, atactile output is generated only when the current value has changed tothe predefined reference value but not when the current value haschanged away from the predefined reference value. In some embodimentsthe tactile output is generated in conjunction with snapping behaviorwhere the current value of the slider snaps to the predefined referencevalue when the current value is moved (in response to user input) withina predefined distance of the predefined reference value.

In some embodiments, immediately prior to detecting the contact on thetouch-sensitive surface 112, the slider (e.g., media playback slider502) has a first value (e.g., as indicated by a position of play head520); while the contact is detected on the touch-sensitive surface, thecurrent value of the slider changes to a second value (e.g., in responseto a dragging input with the contact, such as a movement of play head520-0 along a path from focus selector position 518 a to focus selector518 b of FIG. 5E); and the tactile output occurs (740) in response todetecting that a current value of the slider has changed back to thefirst value in response to user input (e.g., play head 520-0 is returnedto position 518 a from position 518 b). For example, a tactile output isgenerated to indicate that the thumb has returned to its originalposition to provide the user with feedback to enable the user to returnthe original position within the content. In some embodiments, a tactileoutput (e.g., with a same characteristic waveform or a differentcharacteristic waveform from the tactile output provided in conjunctionwith snapping behavior) is generated in response to determining that thecurrent value has changed away from the first value in response to userinput (e.g., when the thumb moves away from the predefined referencevalue). In some embodiments, a tactile output is generated only when thecurrent value has changed to the first value but not when the currentvalue has changed away from the first value. In some embodiments thetactile output is generated in conjunction with snapping behavior wherethe current value of the slider snaps to the first value when thecurrent value is moved (in response to user input) within a predefineddistance of the first value.

It should be understood that the particular order in which theoperations in FIGS. 7A-7D have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,method 800) are also applicable in an analogous manner to method 700described above with respect to FIGS. 7A-7D. For example, the contacts,gestures, user interface objects, tactile outputs, intensity thresholds,focus selectors, and animations described above with reference to method700 optionally have one or more of the characteristics of the contacts,gestures, user interface objects, tactile outputs, intensity thresholds,focus selectors, and animations described herein with reference to othermethods described herein (e.g., method 800). For brevity, these detailsare not repeated here.

FIGS. 8A-8D are flow diagrams illustrating a method 800 of adjusting aproperty of a user interface element in accordance with someembodiments. The method 800 is performed at an electronic device (e.g.,device 300, FIG. 3, or portable multifunction device 100, FIG. 1A) witha display, a touch-sensitive surface, and one or more sensors to detectintensity of contacts with the touch-sensitive surface. In someembodiments, the display is a touch-screen display and thetouch-sensitive surface is on or integrated with the display. In someembodiments, the display is separate from the touch-sensitive surface.Some operations in method 800 are, optionally, combined and/or the orderof some operations is, optionally, changed.

As described below, the method 800 provides an intuitive way to adjust aproperty of a user interface element. The method reduces the number,extent, and/or nature of the inputs from a user when adjusting aproperty of a user interface element, thereby creating a more efficienthuman-machine interface. For battery-operated electronic devices,enabling a user to adjust a property of a user interface element fasterand more efficiently conserves power and increases the time betweenbattery charges.

The device displays (802) a user interface that includes one or moreuser interface elements. For example, user interface elements of a userinterface shown in FIG. 6A include an image message 602, text messages604 and 606, messaging controls 610 and 612, text entry box 614, backbutton 616, messaging information objects 618 and 620, signal strengthindicators 402, time 404, and battery status indicator 406.

The device detects (804) a contact on the touch-sensitive surface 112.For example, the contact is detected at a location indicated by focusselector 624.

While detecting (806) the contact on the touch-sensitive surface 112,the device detects (808) (e.g., with the one or more sensors configuredto detect intensity of contacts on the touch-sensitive surface) a firstincrease in a characteristic intensity of the contact on thetouch-sensitive surface 112. For example, a first increase in thecharacteristic intensity of the contact may be an increase above anintensity threshold IT_(H) (e.g., an increase from the intensity levelindicated by intensity meter 622 shown in FIG. 6A to the intensity levelindicated by intensity meter 622 in FIG. 6B), the first increase in thecharacteristic intensity of the contact may be an increase above anintensity threshold IT_(L) (e.g., an increase from the intensity levelindicated by intensity meter 622 shown in FIG. 6A to the intensity levelindicated by intensity meter 622 in FIG. 6D), or the first increase inthe characteristic intensity of the contact is an increase above anotherstatic or dynamically determined intensity threshold.

In response to detecting the first increase in the characteristicintensity of the contact, the device adjusts (810) a property of a firstuser interface element of the one or more user interface elements in theuser interface from a first value to a second value. For example, asshown in FIG. 6A, a first user interface element is, e.g., image 602 andthe property of the first user interface element is, e.g., anarea/display size of image 602. The area/display size of image 602 isadjusted from an initial value (e.g., as shown in FIG. 6A) to anincreased value (e.g., as shown in FIG. 6B and as shown in FIG. 6D). Insome embodiments, increasing the value of a property of the first userinterface element also increases the value of a corresponding propertyof the entire user interface, such as a magnification level. In someembodiments, an amount of increase in the value of the property isdetermined based on the amount of increase in the characteristicintensity of the contact (e.g., the more the characteristic intensity ofthe contact increases, the more the value of the property increases).

In some embodiments, the property is a magnification factor (812) of thefirst user interface element. For example, the magnification of image602 is adjusted as described with regard to FIGS. 6A-6O. In someembodiments, the area/display size of the user interface element remainsconstant as the magnification factor of the first user interface elementis adjusted. For example, as shown in the transition of image 602 asshown in FIG. 6A to image 602 as shown in FIG. 6O, the area/display sizeof image 602 remains constant as image 602 is magnified. In someembodiments, the area/display size of image 602 increases as themagnification of image 602 is increased. For example, as shown in thetransition of image 602 as shown in FIG. 6C to image 602 as shown inFIG. 6D, the area/display size of image 602 increases as image 602 ismagnified.

In some embodiments, the property is play progress (814) (e.g., the userinterface element is a representation of media content, such as an audiotrack or a video) and adjusting the property includes advancing progressin the media content. For example, progress in an audio track isadvanced from a first point in the audio track, as indicated by aposition of play head 650 along media playback slider 632 in FIG. 6P, toa second point in the audio track, as indicated by a position of playhead 650 along media playback slider 632 in FIG. 6Q. In someembodiments, adjusting play progress occurs when focus selector 624 isat a location of a media playback slider 632, as indicated in FIGS.6P-6Q. In some embodiments, adjusting play progress occurs when focusselector is at a location other than media playback slider 632.

In some embodiments, the property is a volume level (816). For example,a volume level is increased from a first volume level, as indicated by aposition of volume control 652 along volume slider 646 in the userinterface of FIG. 6R, to a second volume level, as indicated by aposition of volume control 652 along volume slider 646 in the userinterface of FIG. 6S. In some embodiments, adjusting the volume leveloccurs when focus selector 624 is at a location of a volume slider 646,as indicated in FIGS. 6R-6S. In some embodiments, adjusting volume leveloccurs when focus selector is at a location other than volume slider646.

In some embodiments, an amount of the adjustment from the first value tothe second value is determined (818) based on the first increase in thecharacteristic intensity of the contact. For example, the amount of theadjustment from the first value to the second value is directlyproportional to an amount of increase in the characteristic intensity.In some embodiments, adjustment from a second value to a third value isdetermined based on a second increase in the characteristic intensity ofthe contact. For example, the amount of the adjustment from the secondvalue to the third value is directly proportional to an amount ofincrease in the characteristic intensity. In some embodiments, an amountof the adjustment from the third value to the first value is based on afirst decrease in the characteristic intensity of the contact. Forexample, the amount of the adjustment from the third value to the firstvalue is directly proportional to an amount of decrease in thecharacteristic intensity.

After adjusting the property of the first user interface element, thedevice detects (820) a first decrease in the characteristic intensity ofthe contact (e.g., a decrease below an intensity threshold IT_(H) asindicated by intensity meter 622). For example, the device detects adecrease as indicated by the transition from the intensity levelindicated by intensity meter 622 shown in FIG. 6D to the intensity levelindicated by intensity meter 622 shown in FIG. 6F.

In response to detecting the first decrease in the characteristicintensity of the contact, in accordance with a determination that thefirst increase in the characteristic intensity of the contact metintensity criteria (e.g., that the characteristic intensity of thecontact increased above a intensity threshold, such as a light pressintensity threshold IT_(L) as indicated by intensity meter 622, oranother statically or dynamically determined intensity threshold), thedevice maintains (822) the property of the first user interface elementabove the first value (e.g., the device maintains the property of thefirst user interface element at the second value). For example, as aresult of an increase in the characteristic intensity of the contactabove IT_(L), as indicated by intensity meter 622 of FIG. 6D, when adecrease in the characteristic intensity of the contact is detected, asindicated by intensity meter 622 of FIG. 6F, the area/display size ofimage 602 is maintained above the initial area/display size of image 602as shown in FIG. 6A. In FIG. 6F, the area/display size of image 602remains at the expanded level (e.g., the expanded area/display size asshown in FIG. 6D).

In some embodiments, maintaining the property of the first userinterface element above the first value in response to detecting thefirst decrease in the characteristic intensity of the contact includes(824) maintaining the property at a constant value above the firstvalue. For example, in response to a detected first decrease in thecharacteristic intensity of the contact, the area of image 602 remainsat the expanded level as shown in FIG. 6F.

In some embodiments, maintaining the property of the first userinterface element above the first value in response to detecting thefirst decrease in intensity of the contact includes (826) reducing theproperty of the first user interface element below the second value. Forexample, as shown in FIG. 6G, in response to a detected first decreasein the characteristic intensity of the contact, the area/display size ofimage 602 decreases to below the expanded level shown in FIG. 6F (e.g.,to produce a “deflation” effect between “inflations” of the property ofthe user interface element in response to detected increases in thecharacteristic intensity of the contact). In some embodiments, reducingthe property of the first user interface element below the second valueis continuous from when (e.g., the instant at which) the first decreasein intensity of the contact is detected until a subsequent increase inintensity of the contact is detected. In some embodiments, reducing theproperty of the first user interface element below the second valuecontinues until the property of the first user interface element returnsto just above the first value (e.g., the area/display size of image 602decreases to just above the area/display size of image 602 shown in FIG.6A), such as within a determined margin of the first value. In someembodiments, the reduction in the property of the first user interfaceelement below the second value is limited to a determined margin of thesecond value (e.g., the reduction in the area/display size of image 602is limited to a 10% reduction in area from the expanded area/displaysize of image 602 as shown in FIG. 6D while the contact with touchscreen 112 is maintained).

In some embodiments, the intensity criteria include (828) a requirementthat the characteristic intensity of the contact increases at or above athreshold rate during the first increase in the characteristicintensity. For example, a quick press (e.g., a jab) by the contact thatthat increases the characteristic intensity of the contact at or above athreshold rate satisfies the intensity criteria.

After detecting the decrease in the characteristic intensity of thecontact and while the property of the first user interface element isabove the first value, the device detects (830) a second increase in thecharacteristic intensity of the contact. For example, a characteristicintensity of the contact increases from the intensity level indicated byintensity meter 622 shown in FIG. 6F to the intensity level indicated byintensity meter 622 shown in FIG. 6H. In some embodiments, the intensitylevel reached by the second increase in the characteristic intensity ofthe contact is the same as, less than, or greater than the intensitylevel reached by the first increase in characteristic intensity.

In response to detecting the second increase in the characteristicintensity of the contact, the device adjusts (832) the property of thefirst user interface element to a third value that is greater than thesecond value. For example, the area/display size of image 602 isadjusted from an expanded value as shown in FIG. 6D to a furtherexpanded value, as shown in FIG. 6H. In some embodiments, the amount ofincrease in the property is determined based on the amount of increasein the characteristic intensity of the contact (e.g., the more thecharacteristic intensity of the contact increases, the more the value ofthe property increases).

In some embodiments, after increasing the property of the first userinterface element to the third value, the device detects (834) liftoffof the contact and the device maintains the property of the first userinterface element above the second value (e.g., the device maintain theproperty of the first user interface at the third value). For example,as shown in FIG. 6N, in response to detecting liftoff of the contactfrom touch sensitive surface 112, the area/display size of image 602 ismaintained above the expanded area/display size of image 602 (e.g., thearea/display size of image 602 is maintained at the further expandedlevel as shown in FIG. 6H). In FIG. 6N, the area/display size of image602 remains at the further expanded level (e.g., the further expandedlevel as shown in FIG. 6J). In some embodiments, maintaining theproperty of the first user interface element above the second value inresponse to detecting the first decrease in intensity of the contactincludes reducing the property of the first user interface element belowthe third value.

In some embodiments, in response to detecting the first decrease in thecharacteristic intensity of the contact, in accordance with adetermination that the first increase in the characteristic intensity ofthe contact did not meet the intensity criteria (e.g., thecharacteristic intensity of the contact did not increase above anintensity threshold, e.g., the light press intensity threshold IT_(L) asindicated by intensity meter 622, or another statically or dynamicallydetermined intensity threshold) the device returns (836) the property ofthe first user interface element to the first value. For example, afteran increase in the area of image 602 occurs, as shown in FIGS. 6A-6B,because the characteristic intensity of the contact did not increaseabove IT_(L) (e.g., as indicated by intensity meter 622 as shown in FIG.6B), when a decrease in the characteristic intensity of the contactoccurs (e.g., as indicated by intensity meter 622 as shown in FIG. 6C),the area/display size of the image 602 is returned to the initial valueof the area/display size of the image (e.g., the area/display size ofimage 602 as shown in FIG. 6C is equal to the initial area/display sizeof image 602 as shown in FIG. 6A).

In some embodiments, after increasing the property of the first userinterface element to the third value, the device detects liftoff of thecontact and the device returns (838) the property of the first userinterface element to the first value. For example, as shown in FIG. 6K,the area/display size of image 602 returns to an initial area/displaysize when liftoff of the contact occurs (e.g., the area/display size ofimage 602 as shown in FIG. 6K is equal to the initial area/display sizeof image 602 as shown in FIG. 6A).

In some embodiments, returning the property of the first user interfaceelement to the first value includes (840) a first portion showing adecrease of the property of the first user interface element from thesecond value to a fourth value, followed by a second portion showing anincrease from the fourth value to the first value. For example, as thearea/display size of image 602 is returned to an initial area/displaysize (e.g., as the area/display size of image 602 is reduced from afurther expanded level as shown in FIG. 6J to an initial level as shownin FIG. 6K, or as the area/display size of image 602 is reduced from anexpanded level as shown in FIG. 6B to an initial level as shown in FIG.6C), the area/display size of image 602 decreases to a reduced level(e.g., decreases from the initial area/display size as shown in FIG. 6Kto a reduced area/display size as shown in FIG. 6L), followed by areturn to the initial area/display size of image 602 (e.g., increasesfrom the reduced area/display size as shown in FIG. 6L to the initialarea/display size as shown in FIG. 6M).

In some embodiments, adjusting the property of the first user interfaceelement from the first value to the second value includes (842) a firstportion showing an increase of the property of the first user interfaceelement from the first value to a fifth value, followed by a secondportion showing a decrease from the fifth value to the second value. Forexample, as the area/display size of image 602 increases from an initialarea/display size (e.g., as shown in FIG. 6A) to an expandedarea/display size (e.g., as shown in FIG. 6F), the expanded area/displaysize increases (e.g., increases from the target expanded area/displaysize as shown in FIG. 6D to a larger area/display size as shown in FIG.6E), followed by a return to the expanded area/display size of image 602(e.g., decreases from the larger area/display size as shown in FIG. 6Eto the target expanded area/display size as shown in FIG. 6F).

In some embodiments, adjusting the property of the first user interfaceelement to the third value includes (844) a first portion showing anincrease of the property of the first user interface element from thesecond value to a sixth value, followed by a second portion showing adecrease from the sixth value to the third value. For example, as thearea/display size of image 602 increases from an expanded area/displaysize (e.g., as shown in FIG. 6F) to a further expanded area/display size(e.g., as shown in FIG. 6H), the further expanded area/display sizeincreases (e.g., increases from the target further expanded area/displaysize as shown in FIG. 6H to a larger area/display size as shown in FIG.6I), followed by a return to the further expanded area/display size ofimage 602 (e.g., decreases from a larger area/display size as shown inFIG. 6I to the target further expanded area/display size as shown inFIG. 6J).

In some embodiments, adjusting the property of the first user interfaceelement includes (846) dynamically adjusting the appearance of the firstuser interface element. For example, a dynamic adjustment of anappearance of the first user interface element includes graphicaladjustment to the entire first user interface element (e.g., adjustingan area of image 602), graphical adjustment along one or more axes ofthe first user interface element (e.g., stretching a first userinterface element in a vertical direction, in a horizontal direction,and/or in a z-axis direction), replacement of a first representation ofthe first user interface element (e.g., document title) with analternative representation of the first user interface element (e.g.,sub-section title), or adjustment of spacing between frames of video.

In some embodiments, the device dynamically adjusts (848) the appearanceof the first user interface element based on detected changes in thecharacteristic intensity of the contact. For example, adjustment of theappearance of the first user interface element is directly proportionalto the characteristic intensity of the contact and/or based on anincrease above or decrease below an intensity threshold.

In some embodiments, the device adjusts (850) the appearance of thefirst user interface element based on a respective increase in thecharacteristic intensity of the contact, wherein the appearance of thefirst user interface element is not adjusted when a respective decreasein the characteristic intensity of the contact occurs. In someembodiments, the dynamic adjustment of the appearance of the first userinterface element only tracks the intensity of the contact when theintensity of the contact is increasing, but does not track the intensityof the contact when the intensity of the contact is decreasing. Forexample, the area of image 602 expands when increases in characteristicintensity of the contact occur (e.g., as indicated by the expansion ofthe area/display size of image 602 as shown in FIG. 6A to thearea/display size of image 602 as shown in FIG. 6D, and as indicated bythe expansion of the area/display size of image 602 as shown in FIG. 6Dto the area/display size of image 602 as shown in FIG. 6F). Thearea/display size of image 602 does not decrease when decreases incharacteristic intensity of the contact occur (e.g., the area/displaysize of image 602 as shown in FIG. 6D is maintained as shown in FIG. 6F,and the area/display size of image 602 as shown in FIG. 6H is maintainedas shown in FIG. 6J).

In some embodiments, the contact is initially detected (852) when afocus selector 624 is at the first user interface element. For example,a contact at a location indicated by focus selector 624 is initiallydetected when the focus selector 624 is at a user interface element(e.g., focus selector 624 is at image 602 as shown in FIGS. 6A-6I, atmedia playback slider 632 as shown in FIGS. 6P-6Q, or at volume control652 as shown in FIGS. 6R-6S).

It should be understood that the particular order in which theoperations in FIGS. 8A-8D have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,method 700) are also applicable in an analogous manner to method 800described above with respect to FIGS. 8A-8D. For example, the contacts,user interface objects, intensity thresholds, focus selectors, andanimations described above with reference to method 800 optionally haveone or more of the characteristics of the contacts, user interfaceobjects, intensity thresholds, focus selectors, and animations describedherein with reference to other methods described herein (e.g., method700). For brevity, these details are not repeated here.

In accordance with some embodiments, FIG. 9 shows a functional blockdiagram of an electronic device 900 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 9 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 9, an electronic device 900 includes a display unit 902configured to display a user interface, a touch-sensitive surface unit904 configured to receive contacts, one or more sensor units 906configured to detect intensity of contacts with the touch-sensitivesurface unit 904; and a processing unit 908 coupled with the displayunit 902, the touch-sensitive surface unit 904 and the one or moresensor units 906. In some embodiments, the processing unit 908 includes:a display enabling unit 910, a detecting unit 912, a maintaining unit914, a shifting unit 916, and a providing unit 918.

The processing unit 908 is configured to: enable display (e.g., withdisplay enabling unit 910), on the display unit 902 of a user interfacethat includes: a slider that corresponds to a first range of values, andone or more other user interface objects; detect (e.g., with detectingunit 912) a contact on the touch-sensitive surface unit while a focusselector is at the slider; detect (e.g., with the detecting unit 912) afirst increase in a characteristic intensity of the contact on thetouch-sensitive surface unit while the focus selector is at the slider;and, in response to detecting the first increase in the characteristicintensity of the contact on the touch-sensitive surface unit and inaccordance with a determination that the characteristic intensity of thecontact meets intensity criteria: enable display (e.g., with displayenabling unit 910) of an expanded portion, less than all, of the sliderwhile maintaining an appearance of the one or more other user interfaceobjects.

In some embodiments, the processing unit 908 is configured to: afterexpanding the slider, detect (e.g., with the detecting unit 912) a firstdecrease in the characteristic intensity of the contact on thetouch-sensitive surface unit while the focus selector is at the slider;in response to detecting the first decrease in the characteristicintensity of the contact, maintain (e.g., with the maintaining unit 914)display of the expanded portion of the slider; after detecting thedecrease in the characteristic intensity of the contact and while theexpanded portion of the slider is displayed, detect (e.g., with thedetecting unit 912) a second increase in the characteristic intensity ofthe contact on the touch-sensitive surface unit while the focus selectoris at the slider; and, in response to detecting the second increase inthe characteristic intensity of the contact, enable display (e.g., withdisplay enabling unit 910) of a further expanded portion of the slider.

In some embodiments, the processing unit 908 is configured to, afterexpanding the slider, detect (e.g., with the detecting unit 912) a firstdecrease in the characteristic intensity of the contact on thetouch-sensitive surface unit while the focus selector is at the slider;and, in response to detecting the first decrease in the characteristicintensity of the contact, enable display (e.g., with display enablingunit 910) of the slider with reduced expansion.

In some embodiments, the processing unit 908 is configured to, inresponse to detecting the first increase in the characteristic intensityof the contact on the touch-sensitive surface unit 904 and in accordancewith a determination that the characteristic intensity of the contactdoes not meet the first intensity criteria, maintain (e.g., with themaintaining unit 914) the appearance of the slider and the one or moreother controls without displaying an expanded portion of the slider.

In some embodiments, enabling display of an expanded portion of theslider includes modifying range indicator values that are displayed onor adjacent to the slider.

In some embodiments, the processing unit 908 is configured to detect(e.g., with the detecting unit 912) movement of the focus selector alongthe slider; and, in response to detecting movement of the focus selectoralong the slider: in accordance with a determination that the firstintensity criteria were met, shift (e.g., with the shifting unit 916) acurrent value of the slider by a first amount; and in accordance with adetermination that the first intensity criteria were not met, shift(e.g., with the shifting unit 916) a current value of the slider by asecond amount different from the first amount.

In some embodiments, initial detection of the contact on thetouch-sensitive surface unit 904 occurs when the focus selector is at alocation of a displayed play head in the slider.

In some embodiments, a thumb control for the slider remains displayedunder the focus selector when the expanded portion of the slider isdisplayed.

In some embodiments, a magnification within the expanded portion of theslider increases as the characteristic intensity of the contactincreases.

In some embodiments, the slider is a progress indicator for mediacontent, the first range of values includes a first sequence of framesof the media content and, enabling display of an expanded portion of theslider includes enabling display of a second sequence of frames of themedia content, wherein spans of time between frames of the firstsequence of frames of the media content are greater than spans of timebetween frames of the second sequence of video frames of the mediacontent.

In some embodiments, the processing unit 908 is configured to: whiledetecting the first increase in the characteristic intensity of thecontact on the touch-sensitive surface unit 904, provide (e.g., with theproviding unit 918), by the touch-sensitive surface unit 904, tactileoutput.

In some embodiments, the tactile output occurs in response to detectingthat a current value of the slider has changed to a predefined referencevalue within the slider in response to user input.

In some embodiments, immediately prior to detecting the contact on thetouch-sensitive surface unit 904, the slider has a first value; whilethe contact is detected on the touch-sensitive surface unit 904, thecurrent value of the slider changes to a second value; and the tactileoutput occurs in response to detecting that a current value of theslider has changed back to the first value in response to user input.

The operations described above with reference to FIGS. 7A-7D are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 9.For example, detection operations 704 and 706 are, optionally,implemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 10 shows a functional blockdiagram of an electronic device 1000 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 10 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 10, an electronic device 1000 includes a display unit1002 configured to display a user interface, a touch-sensitive surfaceunit 1004 configured to receive contacts, one or more sensor units 1006configured to detect intensity of contacts with the touch-sensitivesurface unit 1004; and a processing unit 1008 coupled with the displayunit 1002, the touch-sensitive surface unit 1004 and the one or moresensor units 1006. In some embodiments, the processing unit 1008includes: a display enabling unit 1010, a detecting unit 1012, anadjusting unit 1014, a maintaining unit 1016, and a returning unit 1018.

The processing unit 1008 is configured to enable display (e.g., with thedisplay enabling unit 1010), on the display unit, of a user interfacethat includes one or more user interface elements; detect (e.g., withthe detecting unit 1012) a contact on the touch-sensitive surface unit;and, while detecting the contact on the touch-sensitive surface unit:detect (e.g., with the detecting unit 1012) a first increase in acharacteristic intensity of the contact on the touch-sensitive surfaceunit; in response to detecting the first increase in the characteristicintensity of the contact, adjust (e.g., with the adjusting unit 1014) aproperty of a first user interface element of the one or more userinterface elements in the user interface from a first value to a secondvalue; after adjusting the property of the first user interface element,detect (e.g., with the detecting unit 1012) a first decrease in thecharacteristic intensity of the contact; in response to detecting thefirst decrease in the characteristic intensity of the contact, inaccordance with a determination that the first increase in thecharacteristic intensity of the contact met intensity criteria, maintain(e.g., with the maintaining unit 1016) the property of the first userinterface element above the first value; after detecting the decrease inthe characteristic intensity of the contact and while the property ofthe first user interface element is above the first value, detect (e.g.,with the detecting unit 1012) a second increase in the characteristicintensity of the contact; and, in response to detecting the secondincrease in the characteristic intensity of the contact, adjust (e.g.,with the adjusting unit 1014) the property of the first user interfaceelement to a third value that is greater than the second value.

In some embodiments, the processing unit is configured to, afterincreasing the property of the first user interface element to the thirdvalue, detect (e.g., with the detecting unit 1012) liftoff of thecontact and maintain (e.g., with the maintaining unit 1016) the propertyof the first user interface element above the second value.

In some embodiments, the processing unit is configured to, in responseto detecting the first decrease in the characteristic intensity of thecontact, in accordance with a determination that the first increase inthe characteristic intensity of the contact did not meet the intensitycriteria, return (e.g., with the returning unit 1018) the property ofthe first user interface element to the first value.

In some embodiments, the processing unit is configured to, afterincreasing the property of the first user interface element to the thirdvalue, detect (e.g., with the detecting unit 1012) liftoff of thecontact and return (e.g., with the returning unit 1018) the property ofthe first user interface element to the first value.

In some embodiments, returning the property of the first user interfaceelement to the first value includes a first portion showing a decreaseof the property of the first user interface element from the secondvalue to a fourth value, followed by a second portion showing anincrease from the fourth value to the first value.

In some embodiments, adjusting the property of the first user interfaceelement from the first value to the second value includes a firstportion showing an increase of the property of the first user interfaceelement from the first value to a fifth value, followed by a secondportion showing a decrease from the fifth value to the second value.

In some embodiments, adjusting the property of the first user interfaceelement to the third value includes a first portion showing an increaseof the property of the first user interface element from the secondvalue to a sixth value, followed by a second portion showing a decreasefrom the sixth value to the third value.

In some embodiments, maintaining the property of the first userinterface element above the first value in response to detecting thefirst decrease in the characteristic intensity of the contact includesmaintaining the property at a constant value above the first value.

In some embodiments, maintaining the property of the first userinterface element above the first value in response to detecting thefirst decrease in intensity of the contact includes reducing theproperty of the first user interface element below the second value.

In some embodiments, the property is a magnification factor of the firstuser interface element.

In some embodiments, the property is play progress.

In some embodiments, the property is a volume level.

In some embodiments, an amount of the adjustment from the first value tothe second value is determined based on the first increase in thecharacteristic intensity of the contact.

In some embodiments, adjusting the property of the first user interfaceelement includes dynamically adjusting an appearance of the first userinterface element.

In some embodiments, the processing unit is configured to dynamicallyadjust (e.g., with the adjusting unit 1014) the appearance of the firstuser interface element based on detected changes in the characteristicintensity of the contact.

In some embodiments, the processing unit is configured to adjust (e.g.,with the adjusting unit 1014) the appearance of the first user interfaceelement based on a respective increase in the characteristic intensityof the contact, wherein the appearance of the first user interfaceelement is not adjusted when a respective decrease in the characteristicintensity of the contact occurs.

In some embodiments, the contact is initially detected when a focusselector is at the first user interface element.

In some embodiments, the intensity criteria include a requirement thatthe characteristic intensity of the contact increases at or above athreshold rate during the first increase in the characteristicintensity.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 8A-8D are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.10. For example, detection operations 804 and 806 and adjustingoperations 810 and 832 are, optionally, implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A computer readable storage medium storing one ormore programs, the one or more programs comprising instructions, whichwhen executed by an electronic device with a display, and atouch-sensitive surface, cause the device to: display, on the display, auser interface that includes one or more user interface elements; detecta contact on the touch-sensitive surface; and, while detecting thecontact on the touch-sensitive surface: detect a first increase in acharacteristic intensity of the contact on the touch-sensitive surface;in response to detecting the first increase in the characteristicintensity of the contact, adjusting a property of a first user interfaceelement of the one or more user interface elements in the user interfacefrom a first value to a second value; after adjusting the property ofthe first user interface element, detect a first decrease in thecharacteristic intensity of the contact; in response to detecting thefirst decrease in the characteristic intensity of the contact, inaccordance with a determination that the first increase in thecharacteristic intensity of the contact met intensity criteria, maintainthe property of the first user interface element above the first value;after detecting the decrease in the characteristic intensity of thecontact and while the property of the first user interface element isabove the first value, detect a second increase in the characteristicintensity of the contact; and, in response to detecting the secondincrease in the characteristic intensity of the contact, adjust theproperty of the first user interface element to a third value that isgreater than the second value.
 2. The computer readable storage mediumof claim 1, including instructions which, when executed by theelectronic device, cause the electronic device to, after increasing theproperty of the first user interface element to the third value, detectliftoff of the contact and maintaining the property of the first userinterface element above the second value.
 3. The computer readablestorage medium of claim 1, including instructions which, when executedby the electronic device, cause the electronic device to, in response todetecting the first decrease in the characteristic intensity of thecontact, in accordance with a determination that the first increase inthe characteristic intensity of the contact did not meet the intensitycriteria, return the property of the first user interface element to thefirst value.
 4. The computer readable storage medium of claim 1,including instructions which, when executed by the electronic device,cause the electronic device to, after increasing the property of thefirst user interface element to the third value, detect liftoff of thecontact and returning the property of the first user interface elementto the first value.
 5. The computer readable storage medium of claim 3,wherein returning the property of the first user interface element tothe first value includes a first portion showing a decrease of theproperty of the first user interface element from the second value to afourth value, followed by a second portion showing an increase from thefourth value to the first value.
 6. The computer readable storage mediumof claim 1, wherein adjusting the property of the first user interfaceelement from the first value to the second value includes a firstportion showing an increase of the property of the first user interfaceelement from the first value to a fifth value, followed by a secondportion showing a decrease from the fifth value to the second value. 7.The computer readable storage medium of claim 1, wherein adjusting theproperty of the first user interface element to the third value includesa first portion showing an increase of the property of the first userinterface element from the second value to a sixth value, followed by asecond portion showing a decrease from the sixth value to the thirdvalue.
 8. The computer readable storage medium of claim 1, whereinmaintaining the property of the first user interface element above thefirst value in response to detecting the first decrease in thecharacteristic intensity of the contact includes maintaining theproperty at a constant value above the first value.
 9. The computerreadable storage medium of claim 1, wherein maintaining the property ofthe first user interface element above the first value in response todetecting the first decrease in intensity of the contact includesreducing the property of the first user interface element below thesecond value.
 10. The computer readable storage medium of claim 1,wherein the property is a magnification factor of the first userinterface element.
 11. The computer readable storage medium of claim 1,wherein the property is play progress.
 12. The computer readable storagemedium of claim 1, wherein the property is a volume level.
 13. Thecomputer readable storage medium of claim 1, wherein an amount of theadjustment from the first value to the second value is determined basedon the first increase in the characteristic intensity of the contact.14. The computer readable storage medium of claim 1, wherein adjustingthe property of the first user interface element includes dynamicallyadjusting an appearance of the first user interface element.
 15. Thecomputer readable storage medium of claim 14, including instructionswhich, when executed by the electronic device, cause the electronicdevice to dynamically adjust the appearance of the first user interfaceelement based on detected changes in the characteristic intensity of thecontact.
 16. The computer readable storage medium of claim 14, includinginstructions which, when executed by the electronic device, cause theelectronic device to adjust the appearance of the first user interfaceelement based on a respective increase in the characteristic intensityof the contact, wherein the appearance of the first user interfaceelement is not adjusted when a respective decrease in the characteristicintensity of the contact occurs.
 17. The computer readable storagemedium of claim 1, wherein the contact is initially detected when afocus selector is at the first user interface element.
 18. The computerreadable storage medium of claim 1, wherein the intensity criteriainclude a requirement that the characteristic intensity of the contactincreases at or above a threshold rate during the first increase in thecharacteristic intensity.
 19. An electronic device, comprising: adisplay; a touch-sensitive surface; one or more processors; memory; andone or more programs, wherein the one or more programs are stored in thememory and configured to be executed by the one or more processors, theone or more programs including instructions for: displaying, on thedisplay, a user interface that includes one or more user interfaceelements; detecting a contact on the touch-sensitive surface; and, whiledetecting the contact on the touch-sensitive surface: detecting a firstincrease in a characteristic intensity of the contact on thetouch-sensitive surface; in response to detecting the first increase inthe characteristic intensity of the contact, adjusting a property of afirst user interface element of the one or more user interface elementsin the user interface from a first value to a second value; afteradjusting the property of the first user interface element, detecting afirst decrease in the characteristic intensity of the contact; inresponse to detecting the first decrease in the characteristic intensityof the contact, in accordance with a determination that the firstincrease in the characteristic intensity of the contact met intensitycriteria, maintaining the property of the first user interface elementabove the first value; after detecting the decrease in thecharacteristic intensity of the contact and while the property of thefirst user interface element is above the first value, detecting asecond increase in the characteristic intensity of the contact; and, inresponse to detecting the second increase in the characteristicintensity of the contact, adjusting the property of the first userinterface element to a third value that is greater than the secondvalue.
 20. A method, comprising: at an electronic device with a display,a touch-sensitive surface, and one or more sensors to detect intensityof contacts with the touch-sensitive surface: displaying, on thedisplay, a user interface that includes one or more user interfaceelements; detecting a contact on the touch-sensitive surface; and, whiledetecting the contact on the touch-sensitive surface: detecting a firstincrease in a characteristic intensity of the contact on thetouch-sensitive surface; in response to detecting the first increase inthe characteristic intensity of the contact, adjusting a property of afirst user interface element of the one or more user interface elementsin the user interface from a first value to a second value; afteradjusting the property of the first user interface element, detecting afirst decrease in the characteristic intensity of the contact; inresponse to detecting the first decrease in the characteristic intensityof the contact, in accordance with a determination that the firstincrease in the characteristic intensity of the contact met intensitycriteria, maintaining the property of the first user interface elementabove the first value; after detecting the decrease in thecharacteristic intensity of the contact and while the property of thefirst user interface element is above the first value, detecting asecond increase in the characteristic intensity of the contact; and, inresponse to detecting the second increase in the characteristicintensity of the contact, adjusting the property of the first userinterface element to a third value that is greater than the secondvalue.